The is listed using 'ls' but can't edit it with 'vim' or list it with 'cat'

Discussion in 'Technical' started by MrCompTech, Feb 3, 2011.

  1. MrCompTech

    MrCompTech New Member

    I'm trying to look at my dovecot configuration files.

    I had upgraded the server from FC13 to FC14.
    In the process dovecot was upgraded to a version 2.0.9 that is not compatible with ISPConfig 3.3.0.2.

    I want to get a look at what the configuration files were.
    I am logged in as 'root' via ssh.

    Run 'cd /etc'
    Run 'ls -l dovecot*' and get
    Code:
    drwxr-xr-x 2 root root 4096 Feb  2 17:58 conf.d
    -rw-r--r-- 1 root root 3455 Dec 30 04:42 dovecot.conf
    -rw-r--r-- 1 root root 3478 Feb  1 21:46 dovecot.conf.glb
    -rw-r--r-- 1 root root  334 Feb  1 21:57 dovecot.conf.rpmsave
    -rw-r--r-- 1 root root  334 Feb  1 21:55 dovecot-new.conf
    When I try to view any of these files with 'vim' a new blank file opens so I quit with out saving.

    If I try to list any of these files with 'cat' I get:
    Code:
    cat: dovecot.conf: No such file or directory
    I can view (vim) and list (cat) the php.ini file and it has the same permissions as the files I can't view or list.

    Code:
    -rw-r--r-- 1 root root 69148 Sep 17 20:07 php.ini
    I have rebooted the server with no change in symptoms.

    When I connect using SFTP the dovecot configuration files are not visible.

    Anyone have any ideas on what's going on, how this might have happened or how to fix it?

    Thanks :)
     
    Last edited: Feb 3, 2011
  2. alleks

    alleks Member

    Just for curiosity try this:

    Code:
    #updatedb
    #locate dovecot.conf
    
    If not installed try:
    Code:
    yum install mlocate
    
     
  3. MrCompTech

    MrCompTech New Member

    I got a bit tired of trying to get my system upgrade to work so I did a complete restore. Since I am now back to the system as it was after I upgraded ISPConfig 3 but before I upgraded to FC14 the issue with the files is no longer present.

    I'll probably try to upgrade again after a few weeks and see what happens then.

    Thanks for trying to help :)
     

Share This Page