I cannot answer for others, but for myself it means that I am busy. I also cannot really connect to your server and help you without a support contract. There are limits to the support I can offer for free.
In short, the next steps I would try is to disable “watch”, delete any existing pid file for winbind, make sure it is really stopped by killing any such process using pkill or by getting the pid out of ps. Then I would restart it from pf and see if it is running. Most likely that will fix it. Regards, -- Louis Munro [email protected] :: www.inverse.ca +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) On Jun 16, 2015, at 3:57 , mourik jan heupink <[email protected]> wrote: > Hi, > > The lack of input means that our problem is unsolveable? > > MJ > > On 06/12/2015 09:24 AM, mourik jan heupink wrote: >> Hi Louis, >> >> Winbind seems to be running now, test binds succeeds, but the gui claims >> that winbind is NOT running, and also watch tries to restart it every >> time it runs. >> >> I'm guessing that could mean that it's also looking for a pid in a wrong >> location or so: >>> Jun 12 09:15:04 pfcmd.pl(15723) INFO: watch found incorrectly stopped >>> services: winbindd-our-wkgr.conf (pf::cmd::pf::service::watchService) >>> Jun 12 09:15:04 pfcmd.pl(15723) INFO: Daemon winbindd-our-wkgr.conf took >>> 0.034 seconds to start. (pf::services::manager::launchService) >>> Jun 12 09:16:04 pfcmd.pl(15723) WARN: winbindd-our-wkgr.conf timed out >>> trying to start (pf::services::manager::postStartCleanup) >> >> In chroot winbind logs: >>> ERROR: winbindd is already running. File >>> /usr/local/pf/var/run/winbindd.pid exists and process id 3854 is running. >> >>> If it is, it’s not an obvious one. >>> I just tested this without problem yesterday on fresh installs of >>> CentOS, Debian and Ubuntu. >> This (debian 7) system has been upgraded from packetfence 5.0.0 (or 1), >> don't remember. >> >>> Hard to say without access to your system and the full logs. >>> Systems are unreliable. >>> Without throwing my hands in the air, there is little more for me to go >>> on here. >> Well, I could give you access to the system, of course. We'd discuss >> access details off list, of course. >> >>> Is there anything relevant to this in the logs/httpd.admin.log at the >>> time when you added the domain from the GUI? >>> Or was this an done with the upgrade script? >> First I was required to run the upgrade script. That never worked out, >> it always kept adding INVERSE everywhere. Then I removed the domain, and >> added it as new, new name also. I guess this is why I have (by now >> three) 'old' chroot directories. (pf doesn't seem to delete the chroots, >> when deleting them from the gui) >> >> Would you like access to the system? >> >> Regards, >> MJ >>> >>> Regards, >>> -- >>> Louis Munro >>> [email protected] <mailto:[email protected]> :: www.inverse.ca >>> <http://www.inverse.ca> >>> +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 >>> Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>) >>> and PacketFence (www.packetfence.org <http://www.packetfence.org>) >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> >>> >>> _______________________________________________ >>> PacketFence-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/packetfence-users >>> > > ------------------------------------------------------------------------------ > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
