crond and the pam_loginuid failed opening loginuid problem...

[Grossmann-Grupp]

Hi together...

I have this in my Log Files...

crond[23018]: pam_loginuid(crond:session): set_loginuid failed opening loginuid

thousends again...

I think this can be a reason of changing the SSH Port...
Is this right? And how can I fix this? I think Plesk can't communicate right with changed SSH Port...

Please let me know how I can change this... I think SSH on Port 22 isn't very good... ;-)
So I changed it to another...

King Regards


Jörg

PS: I have to correct the Version of Plesk!!! It's 9.5
I've posted at the wrong Version Forum... *SORRY*

 

[IgorG]

Generally it is not Plesk related issue. Look at following suggestions. I hope it will help:

http://www.tektonic.net/forum/showthread.php?p=7569
http://forums.powervps.com/showthread.php?p=19872

 

[Grossmann-Grupp]

I have to wait...

I have to wait for the daily statusmail...
I post a reply if it works... ;-)

 

[Grossmann-Grupp]

It work's!

Hey Igor...

Thanks for help!
Your way to fix the problem works very fine!
There are no errors in Log-Mail again... ;-)

But one question I have too...
Did you kno a Tool who blocks special Requests?

--------------------- httpd Begin ------------------------

Requests with error response codes
400 Bad Request
/w00tw00t.at.ISC.SANS.DFind: 55 Time(s)

I want to block this effecitv... Did you know a way?

King Regards


Jörg