12.5.30 - Watchdog sends reports saying apache is old ?

[Reqlez]

Hi.

I hate creating so many threads but it seems nobody is reporting this one...

I have watchdog enabled and it keeps sending reports that my Apache 2.4.6 is OLD ( under the Applications "suspect" section of the report ... I checked and i have 2.4.6-31 it seems its fairly recent update ...

Is it too old or is it not too old ? That is the question !

 

[Reqlez]

wait did i mention that the Watchdog service doesn't start automatically every time server restarts ? maybe need a watchdog for the watchdog service lol

 

[serverpoint_tom]

Hi,

Have you tried to reinstall watchdog package ?

 

[vlikhtanskiy]

Hi @Reqlez!

Unfortunately, I cannot reproduce the issue on our test environment.

Could you please post here output of command "plesk version" and output of security scan provided by watchdog.

 

[Reqlez]

Hi,

Have you tried to reinstall watchdog package ?

yup. Every time i reboot server I have to go in and click "enable" on the watchdog under extensions

 

[Reqlez]

Hi @Reqlez!

Unfortunately, I cannot reproduce the issue on our test environment.

Could you please post here output of command "plesk version" and output of security scan provided by watchdog.

Yes my environment is very special indeed, i guess i'm good at breaking things !

[root@http01 ~]# plesk version
Product version: 12.5.30 Update #4
Update date: 2015/09/29 22:09
Build date: 2015/08/26 19:00
OS version: CentOS 7.1.1503
Revision: 344620
Architecture: 64-bit
Wrapper version: 1.2

and the link to the report file is here: http://1drv.ms/1JBvS13

 

[vlikhtanskiy]

Thank you for additional information. I reproduced both issues on our test environment.

I reported bugs with internals IDs PPP-17755 (about Apache) and PPP-17756 (about server restart). I hope they will be fixed in nearest microupdates.

 

[Reqlez]

On another note, do you have a CentOS 7.1 testing environment ? I did install RTM version ( before update 4 ) fresh and i had nothing but issues... getting hard quotas working took me like 4 hours of research and rebooting server over and over. FTP never worked till i modified where the scoreboard file is stored since the /var/run/proftpd directory would not get created automatically at all ... and even after i modified the scoreboard file, i had to manually add entries into the config file to tell Plesk that PROFTPD exists and has scoreboard file here, but even after i did that ... scoreboard shows empty with the setting in there. U can see my other post about the FTP issues.

EDIT: here is a link for FTP issues, thanks for taking a look into other issues! :http://talk.plesk.com/threads/plesk-12-5-rtm-cannot-connect-to-ftp.334726/#post-786880

 

[vlikhtanskiy]

Yes, we daily test Plesk on CentOS 7.1 the same as on all others supported OSes.

We are researching and trying to reproduce your issue with FTP.

 

[mizar]

Regarding watchdog starting issue on server reboot - you can fix it by manually registering in systemd for autostart:

# systemctl enable wdcollect.service monit.service

 

[Reqlez]

Regarding watchdog starting issue on server reboot - you can fix it by manually registering in systemd for autostart:

# systemctl enable wdcollect.service monit.service

I just ran that command, after restarting i get spam that ALL my services are starting ( probably not a bad thing since that lets me know that the server crashed and rebooted so thats great ).

Thanks again !

 

[Reqlez]

almost forgot to ask ... should i be monitoring PHP-FPM (FastCGI Process Manager) ? by default monitoring is disabled ... and i do see the service being OFF when i enable monitoring ( have not tested with users actually connecting to PHP yet maybe it only starts when a user first requests PHP file ? )

 

[mizar]

If you don't have sites with php-fpm, this service will not start, and switching on minitoring does nothing