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

Cannot Access CP After update 9.2.x to 9.2.3

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by Ritey, Nov 15, 2009.

  1. Ritey

    Ritey Guest

    0
     
    Hi

    This is regarding plesk on linux fc

    I have started an update from CP as normal. And i got the initial success email sent back. But after that i cannot access the CP. And when i log into the server with ssh, the port 8443 is not listening when i use netstat. And also it appears that the autoinstaller is still running. It has been running for about an hour now and the following are still in the process list:-

    root 5647 0.0 1.7 127692 72372 ? Ss 09:37 0:03 /usr/local/psa/admin/bin/autoinstaller --enable-xml-output --
    root 5648 0.0 0.0 0 0 ? Z 09:37 0:00 [autoinstaller] <defunct>
    root 7156 0.0 1.7 127692 69156 ? S 09:39 0:00 /usr/local/psa/admin/bin/autoinstaller --enable-xml-output --
    root 7157 0.1 0.5 56936 21740 ? S 09:39 0:07 rpm -U /var/psaupdates/PSA_9.2.3/dist-rpm-FedoraCore-4-x86_64
    root 8661 0.0 0.1 9928 4644 ? S 09:39 0:00 /bin/sh /var/tmp/rpm-tmp.9387 2
    root 9199 0.0 0.0 2780 652 ? D 09:39 0:00 chmod -R 644 /usr/local/psa/admin/htdocs/locales

    It is now 10:43 GMT so obviously something is stuck.

    Please help!!!!
     
  2. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Look at /tmp/autoinstaller3.log
    Is there something useful?
     
  3. Ritey

    Ritey Guest

    0
     
    Unfortunately I have rebooted the server as it was the only way I could stop the thing. So the autoinstaller log just contains stuff i tried since.

    I did fine out that this was probably the process causing the hang...

    chmod -R 644 /usr/local/psa/admin/htdocs/locales

    As when i tried it, it gave same result. It never ended. Even with kill -9. Took a reboot to stop it.

    Now i have the the CP listening on 8443, but when accessing the server it gives http 500 Internal Server error. Which is presumably because the previous upgrade attempt failed. So there is a miss match of stuff in the installation at the moment.

    The mail and web and all else seems to be running ok. But without CP i am pretty blind.
    I even managed to perform a plesk backup without problem.

    So what i need to know now is what is the best way of returning to a usable state?
     
  4. Ritey

    Ritey Guest

    0
     
    A little more poking around in logs.
    This is from the syslog at around the same time....

    Nov 15 09:39:31 plesk kernel: general protection fault: 0000 [1] SMP
    Nov 15 09:39:31 plesk kernel: CPU 1
    Nov 15 09:39:31 plesk kernel: Modules linked in: ipt_MASQUERADE iptable_nat ip_nat iptable_mangle ipt_REJECT xt_tcpudp xt_stat
    e iptable_filter ip_tables x_tables thermal processor fan
    Nov 15 09:39:31 plesk kernel: Pid: 7804, comm: chmod Tainted: G M 2.6.16.20-060620b #1
    Nov 15 09:39:31 plesk kernel: RIP: 0010:[<ffffffff8028e370>] <ffffffff8028e370>{xfs_inode_item_size+24}
    Nov 15 09:39:31 plesk kernel: RSP: 0018:ffff81001a831b40 EFLAGS: 00010202
    Nov 15 09:39:31 plesk kernel: RAX: ffffffff8057bb40 RBX: ffff810069e061a8 RCX: 7fff81005b80d4f0
    Nov 15 09:39:31 plesk kernel: RDX: 0000000000000001 RSI: 0000000000000002 RDI: ffff8100413e9e00
    Nov 15 09:39:31 plesk kernel: RBP: ffff810069e06058 R08: ffff810069e06198 R09: 0000000000000000
    Nov 15 09:39:31 plesk kernel: R10: 0000000000000001 R11: ffff81005b80d4f0 R12: 0000000000000001
    Nov 15 09:39:31 plesk kernel: R13: ffff81011e56a800 R14: ffff81011e56a800 R15: ffffffffffffffff
    Nov 15 09:39:31 plesk kernel: FS: 00002add13ed91e0(0000) GS:ffff81011fc88ac0(0000) knlGS:00000000f7faa6c0
    Nov 15 09:39:31 plesk kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    Nov 15 09:39:31 plesk kernel: CR2: 000000000054d108 CR3: 00000000bd87b000 CR4: 00000000000006e0
    Nov 15 09:39:31 plesk kernel: Process chmod (pid: 7804, threadinfo ffff81001a830000, task ffff8100d6a61520)
    Nov 15 09:39:31 plesk kernel: Stack: ffffffff8029c711 ffff810069e06058 0000000000000000 0000000000000402
    Nov 15 09:39:31 plesk kernel: ffffffff8029c4db 0000000000000000 00000000802ac2ac 0000000000000000
    Nov 15 09:39:31 plesk kernel: 0000000000000000 0000000000000000
    Nov 15 09:39:31 plesk kernel: Call Trace: <ffffffff8029c711>{xfs_trans_count_vecs+43}
    Nov 15 09:39:31 plesk kernel: <ffffffff8029c4db>{_xfs_trans_commit+339} <ffffffff80293be0>{xlog_grant_log_space+594}
    Nov 15 09:39:31 plesk kernel: <ffffffff802a673d>{kmem_zone_alloc+68} <ffffffff802a67a7>{kmem_zone_zalloc+27}
    Nov 15 09:39:31 plesk kernel: <ffffffff8029297a>{xlog_grant_push_ail+55} <ffffffff80291c52>{xfs_log_reserve+179}
    Nov 15 09:39:31 plesk kernel: <ffffffff8018e2e6>{__mark_inode_dirty+226} <ffffffff802ac3b1>{xfs_ichgtime+211}
    Nov 15 09:39:31 plesk kernel: <ffffffff802a1898>{xfs_setattr+2962} <ffffffff802accfc>{linvfs_setattr+278}
    Nov 15 09:39:31 plesk kernel: <ffffffff80186f12>{notify_change+286} <ffffffff8016ebec>{sys_fchmodat+144}
    Nov 15 09:39:31 plesk kernel: <ffffffff80473dc6>{thread_return+0} <ffffffff8018807d>{mntput_no_expire+23}
    Nov 15 09:39:31 plesk kernel: <ffffffff8016f3de>{filp_close+91} <ffffffff8010a85e>{system_call+126}
    Nov 15 09:39:31 plesk kernel:
    Nov 15 09:39:31 plesk kernel: Code: 0f be 81 9d 01 00 00 83 f8 04 0f 87 8e 00 00 00 89 c0 ff 24
    Nov 15 09:39:31 plesk kernel: RIP <ffffffff8028e370>{xfs_inode_item_size+24} RSP <ffff81001a831b40>
    Nov 15 09:39:31 plesk kernel: BUG: chmod/7804, lock held at task exit time!
    Nov 15 09:39:31 plesk kernel: [ffff8100c9658178] {inode_init_once}
    Nov 15 09:39:31 plesk kernel: .. held by: chmod: 7804 [ffff8100d6a61520, 118]
    Nov 15 09:39:31 plesk kernel: ... acquired at: sys_fchmodat+0x5b/0xb5


    So it seems that it is the chmod. "lock help at task exit time!"
     
  5. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Hmm... According google seems it is kernel bug. Did you tried upgrade kernel there? Not sure that it is Plesk related issue. I can suggest you also try to install psa packages with something like 'rpm -Uvh --force --nodeps psaxxxx.rpm'
    All necessary default chowns and chmods will be applied correctly and maybe it will help too.
     
  6. Ritey

    Ritey Guest

    0
     
    Thanks for looking at that. I did try the rpm but with --force, did not use --nodeps. And that would explain why i got dependency errors when i tried.

    I will try that first. Failing that i will re-image the server. It seems that my host (1and1) has droped FC4 in favour of centos/plesk 9.

    That being the case, i have successfully made a full plesk backup (even though it was after the problem). Is restoring my data to a new install of plesk on a new OS, just a case of the pleskrestore utility? If so then hopefully that will cure the kernel bug issue also.
     
  7. Ritey

    Ritey Guest

    0
     
    Thanks your advice worked. I now have my plesk CP back!
    I think i will possibly leave the re image until i refill my fridge with beer.

    Thanks for your help!
     
Loading...