1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Issue with xinetd. Need assistance

Discussion in 'Plesk for Linux - 8.x and Older' started by acidbox, Nov 23, 2005.

  1. acidbox

    acidbox Guest

    0
     
    I checked my /var/log/messages this morning and I'm getting thousands of messages like this:

    I've tried restarting xinetd and qmail with no resolve. The process looks like this:

    # ps -aux | grep xinetd
    Code:
    root      7928  0.1  0.0  2148  928 ?        S    Nov22   2:16 xinetd -stayalive -pidfile /var/run/xinetd.pid
    root     30944  0.0  0.0  2148  932 ?        S    17:00   0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
    
    /var/run/xinetd.pid contains:
    30944 refers back to the process listed above. Beyond this, I have no clue what this means.

    Does anyone know what this means and how to fix it?
     
  2. rvdmeer

    rvdmeer Guest

    0
     
    Check the file /etc/xinitd.d/poppassd_psa

    On a fedora core 3 server it should look like this:

     
  3. acidbox

    acidbox Guest

    0
     
    I'm on RHEL3 and mine looks like this:

    Appears to be the same as yours. I haven't made any changes to anything related to this, and it's been running fine for months, which is why I find this error odd.
     
  4. rvdmeer

    rvdmeer Guest

    0
     
    There are 2 pids running?

    Hmmm on a normal server ther is just one pid running. they might fight with eachother.. i would recommend killing the pid. The only thing is.. be sure you 're able to reboot the server with a powerswitch if something goes wrong with connections.
     
  5. acidbox

    acidbox Guest

    0
     
    I know. weird.

    after restarting, i still show:

    Code:
    root      7928  0.1  0.0  2148  928 ?        S    Nov22   2:16 xinetd -stayalive -pidfile /var/run/xinetd.pid
    root     32752  0.0  0.0  2152  940 ?        S    17:26   0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
    
    I checked the messages log and I see that just before the error started, I got this:

    Code:
    Nov 22 11:38:15 edge xinetd[7928]: pmap_set failed. service=sgi_fam program=391002 version=2
    Nov 22 11:38:15 edge xinetd[7929]: pmap_set failed. service=sgi_fam program=391002 version=2
    
    And right before that, it appears that BIND restarted and qmail restarted.
     
  6. rvdmeer

    rvdmeer Guest

    0
     
    i corrected by post:

     
  7. acidbox

    acidbox Guest

    0
     
    do you think rebooting the server might fix it?
     
  8. rvdmeer

    rvdmeer Guest

    0
     
    We'll.. i think killing pid: 7928 will fix it as well.
    But i'm not sure of that. And because when killing a pid on something network based you must be able to restore from that with a powerswitch. If your server is not connected to a powerswitch i would recommend rebooting it.
     
  9. acidbox

    acidbox Guest

    0
     
    Thanks for the help.

    I killed the PID and then restarted xinetd. That seems to have fixed it.

    I now get:

    Code:
    Nov 23 17:32:32 edge xinetd: xinetd shutdown succeeded
    Nov 23 17:32:32 edge xinetd: xinetd startup succeeded
    Nov 23 17:32:32 edge xinetd[564]: pmap_set failed. service=sgi_fam program=391002 version=2
    Nov 23 17:32:33 edge xinetd[564]: xinetd Version 2.3.12 started with libwrap loadavg options compiled in.
    Nov 23 17:32:33 edge xinetd[564]: Started working: 7 available services
    
    with no errors after it.
     
  10. rvdmeer

    rvdmeer Guest

    0
     
    I think those 2 processes where fighting with eachother :)
     
  11. acidbox

    acidbox Guest

    0
     
    Not sure how that got started. One thing I see that looks like an issue is:

    Code:
    Nov 23 17:32:32 edge xinetd[564]: pmap_set failed. service=sgi_fam program=391002 version=2
    
    Do you know what that means?
     
  12. rvdmeer

    rvdmeer Guest

    0
     
  13. acidbox

    acidbox Guest

    0
     
    Thanks.

    It looks like this post was the answer.

    Basically my portmap service wasn't started.

    Code:
    service portmap start
    service xinetd restart
    
    That did the trick!

    Thanks.
     
Loading...