Re: Sogo doesn't start

2014-11-25 Thread Martijn Rijkeboer
Hi, > as a temporary workaround, I haven't tried it yet, maybe it would help > preventing access configure: > > -WOHttpAllowHost 127.0.0.1 > > either as command line parameter, or with defaults write or in sogo.conf. > whereever you prefer ;) Thanks for your suggestion, but for now the PF rules w

Re: Sogo doesn't start

2014-11-25 Thread Sebastian Reitenbach
On Tuesday, November 25, 2014 16:32 CET, "Martijn Rijkeboer" wrote: > Hi, > > > I've just upgrade my server to 5.6 and having trouble starting > > Sogo. When starting Sogo I get the following error: > > > > [ERROR] <0x0x99ae0049590[WOWatchDog]> unable to listen on specified > > port, ch

Re: Sogo doesn't start

2014-11-25 Thread Giovanni Bechis
On 11/25/14 15:22, Martijn Rijkeboer wrote: > Hi > > I've just upgrade my server to 5.6 and having trouble starting Sogo. When > starting Sogo I get the following error: > > [ERROR] <0x0x99ae0049590[WOWatchDog]> unable to listen on specified > port, check that no other process is already usin

Re: Sogo doesn't start

2014-11-25 Thread Martijn Rijkeboer
Hi, > I've just upgrade my server to 5.6 and having trouble starting > Sogo. When starting Sogo I get the following error: > > [ERROR] <0x0x99ae0049590[WOWatchDog]> unable to listen on specified > port, check that no other process is already using it > > I've configured Sogo to use 127.0.0.1:2

Sogo doesn't start

2014-11-25 Thread Martijn Rijkeboer
Hi I've just upgrade my server to 5.6 and having trouble starting Sogo. When starting Sogo I get the following error: [ERROR] <0x0x99ae0049590[WOWatchDog]> unable to listen on specified port, check that no other process is already using it I've configured Sogo to use 127.0.0.1:2 and nets