Hello Chaim, on my machines with SOGo the sogo daemon doas not read the sogo.conf directly but reads whatever "defaults read" exposes.
defaults(1) - read or modify GNUstep user defaults Show us the output of "defaults read" as the user that sogo runs as! Marcus users@sogo.nu (Chaim Litvin), 2020.07.28 (Tue) 08:16 (CEST): > Hi Odhiambo, > > That exactly what I did - sudo user and performed a search but no soo.conf > files was found and got: > > Jul 28 09:02:21 * systemd[1]: Stopping LSB: SOGo server... > > Jul 28 09:02:21 * sogo[18222]: * Stopping SOGo sogo > > Jul 28 09:02:21 * sogo[18222]: ...done. > > Jul 28 09:02:21 * systemd[1]: Stopped LSB: SOGo server. > > Jul 28 09:02:21 * systemd[1]: Starting LSB: SOGo server... > > Jul 28 09:02:21 * sogo[18293]: * Starting SOGo sogo > > Jul 28 09:02:21 * sogo[18293]: ...done. > > Jul 28 09:02:21 * systemd[1]: Started LSB: SOGo server. > > On syslog and from sogo.log > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b76a20[WOWatchDogChild]> sending > terminate signal to pid 5711 > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b76970[WOWatchDogChild]> sending > terminate signal to pid 5710 > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b76650[WOWatchDogChild]> sending > terminate signal to pid 5709 > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b765a0[WOWatchDogChild]> sending > terminate signal to pid 5708 > > Jul 28 06:02:21 sogod [5706]: <0x0x5647988785e0[WOWatchDog]> Terminating with > SIGINT or SIGTERM > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b76650[WOWatchDogChild]> child 5709 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b76a20[WOWatchDogChild]> child 5711 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b76fc0[WOWatchDogChild]> child 5712 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b77300[WOWatchDogChild]> child 5713 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b77870[WOWatchDogChild]> child 5715 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b76970[WOWatchDogChild]> child 5710 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b77920[WOWatchDogChild]> child 5716 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b765a0[WOWatchDogChild]> child 5708 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b77450[WOWatchDogChild]> child 5714 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x564798b77b80[WOWatchDogChild]> child 5717 > exited > > Jul 28 06:02:21 sogod [5706]: <0x0x5647988785e0[WOWatchDog]> all children > exited. We now terminate. > > Jul 28 06:02:21 sogod [18367]: version 4.3.0 (build @shiva2.inverse > 202004020653) -- starting > > Jul 28 06:02:21 sogod [18367]: vmem size check enabled: shutting down app > when vmem > 384 MB. Currently at 224 MB > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5cb7650[SOGoProductLoader]> SOGo > products loaded from '/usr/lib/GNUstep/SOGo': > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5cb7650[SOGoProductLoader]> > PreferencesUI.SOGo, MailPartViewers.SOGo, AdministrationUI.SOGo, > SchedulerUI.SOGo, Contacts.SOGo, ContactsUI.SOGo, Appointments.SOGo, > MailerUI.SOGo, Mailer.SOGo, CommonUI.SOGo, MainUI.SOGo, ActiveSync.SOGo > > Jul 28 06:02:21 sogod [18367]: All products loaded - current memory usage at > 278 MB > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> listening on > 127.0.0.1:20000 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> watchdog > process pid: 18367 > > Jul 28 06:02:21 sogod [18367]: <0x0x7f7e70a7f240[WOWatchDogChild]> watchdog > request timeout set to 10 minutes > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> preparing 10 > children > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18369 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18370 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18371 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18372 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18373 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18374 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18375 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18376 > > Jul 28 06:02:21 sogod [18367]: <0x0x5653b5aa45e0[WOWatchDog]> child spawned > with pid 18377 > > Jul 28 06:02:21 sogod [18369]: [ERROR] |SOGo| No value specified for > 'SOGoProfileURL' > > > > > > it not able to authenticate however the process is running. > > Any ideas? > > Best regards, > > Chaim > > > > > > > > ________________________________ > From: users-requ...@sogo.nu <users-requ...@sogo.nu> on behalf of Odhiambo > Washington <users@sogo.nu> > Sent: Monday, July 27, 2020 7:18:35 PM > To: users@sogo.nu > Subject: Re: [SOGo] sogo.conf > > > > On Mon, 27 Jul 2020 at 18:51, Chaim Litvin > <users@sogo.nu<mailto:users@sogo.nu>> wrote: > Hello, > i have newly installed sogo (Version 4.3.0 @shiva2.inverse 202004020653)+ > nginx server. > login page loaded successfully. > On server startup sogo.log have following eror: > [ERROR] |SOGo| No value specified for 'SOGoProfileURL' > > i checked /etc/sogo/sogo.conf and > SOGoProfileURL = "mysql://sogo:*******@****:3306/sogo/sogo_user_profile"; > > then i renamed sogo.conf and made sure that no additional sogo.conf existed > on system. > after restarting server seems that sogo was able to start service without > config file. > Now i got to conclusion that my server simply ignore sogo.conf file. > Will appreciate your assistance. > > find / -type f -name "sogo.conf" > > It's inconceivable that it can run and access the DB without any credentials. -- users@sogo.nu https://inverse.ca/sogo/lists