Skip to Content.
Sympa Menu

en - Re: [sympa-users] Broken Pipe

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Edward Muller <address@concealed>
  • To: address@concealed
  • Cc: address@concealed
  • Subject: Re: [sympa-users] Broken Pipe
  • Date: 03 Jan 2002 20:19:14 -0500

Nevermind. syslog for some reason did not start on the machine.

So just so you know there is no useful error message displayed by sympa
when syslog is configured and it's not started.

So, I guess I have bigger problems if for some reason syslog did not
start. :-(

Althougt that could be due to the init scripts and checking
/var/lock/subsys in mandrake ... dunno ... will have too look further
...



On Thu, 2002-01-03 at 19:11, address@concealed wrote:
> My server running sympa (v3.2.1) crashed. I'm running a journaled fs and
> rebooted. Everything is working okay, except for sympa. I get the following
> when I attempt to start it manually using ./sympa.pl -d ...
>
> 1010103029 Configuration file read
> 1010103029 List::probe_db()
> 1010103029 List::db_connect
> Broken pipe
>
> if I run strace ./sympa.pl I get the following:
> (just showing the last few lines ... a lot of strace output)....
>
> connect(4, {sin_family=AF_INET, sin_port=htons(5432),
> sin_addr=inet_addr("127.0.0.1")}}, 16) = -1 EINPROGRESS
> (Operation now in progress)
> select(5, [], [4], [4], NULL) = 1 (out [4])
> getsockopt(4, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
> getsockname(4, {sin_family=AF_INET, sin_port=htons(32910),
> sin_addr=inet_addr("127.0.0.1")}}, [16]) = 0
> select(5, [], [4], [4], NULL) = 1 (out [4])
> rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
> send(4, "\0\0\1(\0\2\0\0sympa\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 296,
> 0) = 296
> rt_sigaction(SIGPIPE, {SIG_DFL}, {SIG_IGN}, 8) = 0
> select(5, [4], [], [4], NULL) = 1 (in [4])
> recv(4, "R\0\0\0\0K\0\0\0228T3t\240Z", 16384, 0) = 15
> rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
> send(4, "Qselect getdatabaseencoding()\0", 30, 0) = 30
> rt_sigaction(SIGPIPE, {SIG_DFL}, {SIG_IGN}, 8) = 0
> select(5, [4], [], [4], NULL) = 1 (in [4])
> recv(4, "Pblank\0T\0\1getdatabaseencoding\0\0\0"..., 16384, 0) = 64
> rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
> send(4, "QSET DATESTYLE TO \'ISO\';\0", 25, 0) = 25
> rt_sigaction(SIGPIPE, {SIG_DFL}, {SIG_IGN}, 8) = 0
> select(5, [4], [], [4], NULL) = 1 (in [4])
> recv(4, "CSET VARIABLE\0Z", 16384, 0) = 15
> rt_sigprocmask(SIG_BLOCK, NULL, [32], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [32], 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [32], 8) = 0
> send(3, "<135>sympa[4663]: Connected to D"..., 47, 0) = -1 EPIPE (Broken
> pipe)
> --- SIGPIPE (Broken pipe) ---
> +++ killed by SIGPIPE +++
>
> It looks like it's trying to connect to the database (Postgres) and it's
> getting their, but then the pipe is broken.
>
> I'm able to log into the Postgres database as the sympa user either via
> psql sympa sympa or via webpg (formerly phpPgAdmin). I can do a select *
> from both sympa tables with no problem. And postgres doesn't show anything
> wrong in it's log files.
>
> Help!
--
-------------------------------
Edward Muller
Director of IS

973-715-0230 (cell)
212-487-9064 x115 (NYC)

http://www.learningpatterns.com
-------------------------------



  • Broken Pipe, emuller, 01/04/2002
    • Re: [sympa-users] Broken Pipe, Edward Muller, 01/04/2002

Archive powered by MHonArc 2.6.19+.

Top of Page