Results 1 to 18 of 18
  1. #1
    Join Date
    Jan 2011
    Posts
    99

    Angry TMP file and phpmyadmin

    hi


    i have some problem with TMP file and phpmyadmin!!
    i get this mail from cpanel

    Attempts to create new directories or files whose filenames begin with numbers have failed.
    This is indicative of a root compromise of the server.

    The exact error encountered was:

    Failed to create directory /tmp/cpanel.TMP.2TaRTkfElwYpJNJS: Read-only file system


    and in phpmyadmin i cant access!!!

    how i can fix this?

  2. #2
    Join Date
    Nov 2010
    Location
    Arizona
    Posts
    297
    Try running /scripts/securetmp

  3. #3
    Join Date
    Jan 2011
    Posts
    99
    i do that and i get :


    [email protected] [~]# /scripts/securetmp
    Would you like to secure /tmp & /var/tmp at boot time? (y/n) y
    Would you like to secure /tmp & /var/tmp now? (y/n) y
    Securing /tmp & /var/tmp
    /tmp is already secure
    /var/tmp is already secure
    Checking fstab for entries ...Done
    Logrotate TMPDIR already configured
    Process Complete


    but i steal have problem

  4. #4
    Join Date
    Apr 2009
    Posts
    211
    /tmp directory should be available for writing to everyone, check this.
    █▌KVM-based SSD VPS
    ▌Unmetered Dedicated Servers
    ▌Colocation at 100 Delawanna Ave, Clifton, NJ

  5. #5
    Join Date
    Jan 2011
    Posts
    99
    how i can do that???

  6. #6
    Join Date
    Apr 2009
    Posts
    211
    Just try:
    touch /tmp/1
    If this fails, then something is wrong with /tmp partition and you should show "mount" output.
    █▌KVM-based SSD VPS
    ▌Unmetered Dedicated Servers
    ▌Colocation at 100 Delawanna Ave, Clifton, NJ

  7. #7
    Join Date
    Jan 2011
    Posts
    99
    i get this

    [email protected] [~]# touch /tmp/1
    touch: cannot touch `/tmp/1': Read-only file system

  8. #8
    Join Date
    May 2008
    Location
    Citrus Heights, CA
    Posts
    1,716
    It's probably mounted read only.

    Can you post the output of "mount"
    Best Regards,

    Mark

  9. #9
    Join Date
    Jan 2011
    Posts
    99
    im sorry im very new in dedicated servers and i dont know how do that!
    how i can see "mount"

  10. #10
    Join Date
    Jan 2011
    Posts
    99
    i do something but i dont know if that u mean

    [email protected] [~]# mount
    /dev/sda3 on / type ext3 (rw,usrquota)
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    devpts on /dev/pts type devpts (rw,gid=5,mode=620)
    /dev/sda1 on /boot type ext3 (rw)
    tmpfs on /dev/shm type tmpfs (rw)
    none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
    /usr/tmpDSK on /tmp type ext3 (rw,noexec,nosuid,loop=/dev/loop0)
    /tmp on /var/tmp type none (rw,noexec,nosuid,bind)
    sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

  11. #11
    Join Date
    Dec 2005
    Location
    Swansea, United Kingdom
    Posts
    348
    What's the output of "df -h" ?

  12. #12
    Join Date
    Jan 2011
    Posts
    99
    [email protected] [~]# df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda3 448G 172G 253G 41% /
    /dev/sda1 99M 17M 78M 18% /boot
    tmpfs 1009M 0 1009M 0% /dev/shm
    /usr/tmpDSK 485M 226M 234M 50% /tmp
    [email protected] [~]#

  13. #13
    Join Date
    Sep 2010
    Location
    home
    Posts
    515
    try

    chmod 1777 /tmp

  14. #14
    Join Date
    Jan 2011
    Posts
    99
    Quote Originally Posted by care4server View Post
    try

    chmod 1777 /tmp
    i do that but i still have the problem

  15. #15
    Join Date
    Apr 2009
    Posts
    211
    The easiest way to fix it and keep secure tmp is to stop all services that use /tmp /var/tmp partitions.
    You can detect them by running:

    "lsof /var/tmp"
    "lsof /tmp"

    Sure lsof should be already installed in your system
    and unmount both (/var/tmp should be unmounted first):
    "unmount /var/tmp"
    "unmount /tmp"

    After that try to fix /usr/tmpDSK by
    "e2fsck -y /usr/tmpDSK"

    If this works, try "mount -a" and if you can see both /tmp and /var/tmp after that in output of the "mount" command you should start all services again.
    █▌KVM-based SSD VPS
    ▌Unmetered Dedicated Servers
    ▌Colocation at 100 Delawanna Ave, Clifton, NJ

  16. #16
    Join Date
    Jan 2011
    Posts
    99
    Quote Originally Posted by Natcoweb View Post
    The easiest way to fix it and keep secure tmp is to stop all services that use /tmp /var/tmp partitions.
    You can detect them by running:

    "lsof /var/tmp"
    "lsof /tmp"

    Sure lsof should be already installed in your system
    and unmount both (/var/tmp should be unmounted first):
    "unmount /var/tmp"
    "unmount /tmp"

    After that try to fix /usr/tmpDSK by
    "e2fsck -y /usr/tmpDSK"

    If this works, try "mount -a" and if you can see both /tmp and /var/tmp after that in output of the "mount" command you should start all services again.
    how i can install lsof ??

  17. #17
    Join Date
    Jun 2010
    Location
    Connecticut
    Posts
    128
    Such "read only filesystem" errors can occur due to problems with the physical disk where the filesystem exists. Please check the "dmesg" output for any unusual disk or RAID controller errors.
    OLM.net - Web Hosting Solutions @ Your Service
    Multihomed TIER-1 Network | 24/7 On-site Staff
    IPv6 Now Available! | Dedicated, Virtual, and Shared Hosting
    Hosting in Connecticut Since 1996 - 1-800-741-6813

  18. #18
    Join Date
    Jan 2011
    Posts
    99
    i get this

    [email protected] [~]#dmesg
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    TCP: Treason uncloaked! Peer 11.11.111.111:51521/80 shrinks window 4228345151:4228349507. Repaired.
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    EXT3-fs error (device loop0): ext3_lookup: unlinked inode 6233 in dir #2
    EXT3-fs error (device loop0): ext3_lookup: unlinked inode 6189 in dir #2
    EXT3-fs error (device loop0): ext3_lookup: unlinked inode 6226 in dir #2
    EXT3-fs error (device loop0): ext3_lookup: unlinked inode 6175 in dir #2
    EXT3-fs error (device loop0): ext3_lookup: unlinked inode 6176 in dir #2
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48
    IPv6 addrconf: prefix with wrong length 48

Similar Threads

  1. File: /tmp/sessionv nobody:nobody (99:99)
    By monitor2000com in forum Hosting Security and Technology
    Replies: 10
    Last Post: 01-18-2011, 04:08 AM
  2. /tmp file
    By Fortunehosting in forum Hosting Security and Technology
    Replies: 5
    Last Post: 06-25-2009, 06:05 PM
  3. phpmyadmin & /tmp permissions
    By Ks Jeppe in forum Hosting Security and Technology
    Replies: 3
    Last Post: 11-30-2006, 04:19 PM
  4. Strange File In /tmp (What is it?)
    By sonixi in forum Hosting Security and Technology
    Replies: 4
    Last Post: 09-23-2004, 05:19 PM
  5. Strange file in /tmp... I think
    By BeerHandle in forum Hosting Security and Technology
    Replies: 5
    Last Post: 05-21-2004, 06:45 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •