Re: [Nufw-users] Segmentation fault using postgresql logs

[Vincent SCHULTZ]

Good morning all,

I aplied the patch, set debug mode on Postgresq, here are the result on nuauth 
server :

# /opt/nufw/sbin/nuauth  -vvvvvvvvvv
** Message: debug_level is 9
** Message: Starting nuauth
** Message: Auth (user) module: plaintext
** Message: ACL module: libplaintext
** Message: User logs module: pgsql
** Message: creating acl cache thread
** Message: Creating search_and_fill thread
** Message: Creating 10 acl checkers
** Message: Creating 3 user checkers
** Message: Creating 10 user loggers
** Message: Creating 10 decision workers
** Message: Creating tls authentication server thread
** Message: Creating tls nufw server thread
** Message: Threads system started
** Message: [plaintext] read_user_list: reading [/etc/nufw/users.nufw]
** Message: Going to init pgsql connection
** Message: ...
** Message: Pgsql init done
** Message: [plaintext] read_acl_list: reading [/etc/nufw/acls.nufw]
** Message: [plaintext] Checking for OS sysname=[Linux]
** Message: [plaintext] OS match (Linux)
** Message: [plaintext] Checking for App=[/usr/lib/firefox-1.0.4/firefox-bin]
** Message: Going to init pgsql connection
** Message: ...
** Message: Pgsql init done
Erreur de segmentation

Some logs of postgresql :

TRACE:  Le système de bases de données est prêt
DEBUG:  proc_exit(0)
DEBUG:  shmem_exit(0)
DEBUG:  exit(0)
DEBUG:  reaping dead processes
DEBUG:  forked new backend, pid=7454 socket=9
DEBUG:  /usr/bin/postmaster child[7454]: starting with (
DEBUG:          postgres
DEBUG:          -d5
DEBUG:          -v196608
DEBUG:          -p
DEBUG:          nufwdb
DEBUG:  )
DEBUG:  InitPostgres
DEBUG:  StartTransactionCommand
TRACE:  instruction : INSERT INTO ulog 
(username,user_id,oob_time_sec,ip_protocol,ip_saddr,ip_daddr,tcp_sport,tcp_dport,state,oob_prefix,client_os,client_app)
 VALUES ('No User 
Given',0,1117744382,6,'192.168.6.98','212.85.153.253',42014,80,0,'DROP','','');
DEBUG:  forked new backend, pid=7455 socket=9
DEBUG:  /usr/bin/postmaster child[7455]: starting with (
DEBUG:          postgres
DEBUG:          -d5
DEBUG:          -v196608
DEBUG:          -p
DEBUG:          nufwdb
DEBUG:  )
DEBUG:  InitPostgres
DEBUG:  StartTransactionCommand
TRACE:  instruction : UPDATE ulog SET end_timestamp=Thu Jun  2 20:33:00 2005
        , state=3 WHERE (ip_saddr='192.168.6.98' and tcp_sport=42014 and 
(state=1 or state=2))
ERREUR:  syntax error sur ou près de «Jun» au caractère 35
DEBUG:  AbortCurrentTransaction
TRACE:  Fin de fichier (EOF) inattendue de la connexion du client
DEBUG:  proc_exit(0)
DEBUG:  shmem_exit(0)
DEBUG:  exit(0)
DEBUG:  reaping dead processes
DEBUG:  processus fils (PID 7455) a quitte avec le code de sortie 0
DEBUG:  parse tree:

... some detailled log after.

A problem with the SQL instruction ??

Thanks,

Vincent

Le jeudi 02 juin 2005 à 00:57 +0200, Eric Leblond a écrit :
Le mercredi 01 juin 2005 à 23:09 +0200, Vincent Schultz a écrit :
> > Bonjour la liste,
> 
> boonsoir ;-)
> 
> 
> > ** Message: Going to init pgsql connection
> > ** Message: ...
> > ** Message: done
> > ** Message: ...
> > ** Message: done
> > Erreur de segmentation
> 
> That's really strange, the "done" message is only written. Can you try
> to apply the provided patch which will ease debugging ? 
> 
> > 
> > Postgresql's logs :
> > 
> > ERREUR:  Droit refusé pour la relation ulog
> > ERREUR:  syntax error sur ou près de «Jun» au caractère 35
> > TRACE:  Fin de fichier (EOF) inattendue de la connexion du client
> > TRACE:  Fin de fichier (EOF) inattendue de la connexion du client
> 
> Could you increase verbosity level to be able to have the PGSQL complete
> request.
> 
> > 
> > I think I made a mistake with the rights. This is how I created the
> > database and the user :
> 
> But it should not crash anyway.
> 
> > 
> > # su – postgres
> > $ createuser -D -A -P nufwuser
> > $ createdb nufwdb
> > $ psql nufwdb
> > nufwdb=# \i /tmp/nufw-20050530/conf/nulog.pgsql.dump
> > nufwdb=# GRANT ALL ON DATABASE nufwdb TO nufwuser;
> > 
> > If nuauth_user_logs_module is set on "syslog" instead of "pgsql"
> > everything is fine.
> 
> Is the password empty ? it may be a problem in credential generation.
> Could you try with a non empty one ?
> 
> BR,
>