Topic: Need suggestions -can't access my files

[janet]

Bluephoton

Yes, use the mv command instead
I edited the original

Try it first to play safe on one or a few files eg

mv /home/e-smith/files/ibays/user1/home/filename.ext  /home/e-smith/files/ibays/ibay1/files/

You could also move a single folder as a test eg

mv /home/e-smith/files/ibays/user1/home/foldername  /home/e-smith/files/ibays/ibay1/files/

how would you enter a command ...

Login as root rather than admin. As you seem to be a newbie, be very careful and double check the commands you type before you hit the enter button.
At the command prompt you can seriously damage your server in 1 second

to finish type
exit
press Enter

You seriously need to read the Manuals.

[janet]

Bluephoton

What is the result ?

[Bluephoton]

I had to get some sleep I will try it today while I am fresh - in my time zone it was 2:30 am.

[Bluephoton]

Following your instructions I successfully created the group "group1" and made user1 a member of the group.

I created an ibay "ibay1" and made it owned by group1 with options read and write.

When I click the save button for the ibay create the server crashes and continuously outputs the following error message:

Syntax error on line 615 of
'etc/httpd/conf/httpd.conf:615: <Directory> was not closed

If I control alt delete it reboots and gives the same message once it hits the start process "httpd-e-smith" line and will not boot.

I can boot interactively and bypass that line then reconfigure in the console with a slightly different domain name and reboot and it reboots again to the console.

I have tried twice with the same result.

I have noticed during every boot I get the remark

rm: cannot remove '/var/run/dovecot/login': is a directory

[janet]

Bluephoton

rm: cannot remove '/var/run/dovecot/login': is a directory

Please search on errors before posting, in this case try the Google Custom Search field at top of forums. This is log noise and can be safely ignored, see bug report on the topic (search for it).

Syntax error on line 615 of
'etc/httpd/conf/httpd.conf:615: <Directory> was not closed

As for your httpd.conf error, you need to stop trying to fix it with workarounds ie changing the domain name, as whenever you try to make other system changes, an error reappears.
Concentrate now on the source of that problem and fix it.

Did you look in the file referred to, what does it say on that line number ?
Is there anything you (unwisely) did to your server to cause that problem, you seemed to say you did something before. It is easier if you tell us what you did and then we can tell you how to undo that, ie put it back to normal.

You were given some instructions earlier, so please follow them, rather than going off doing your own thing, and prolonging the process and using up more of our time unnecessarily.

[Bluephoton]

At this point I am going to go and spend some time learning basic Linux as I don't know how to look at the file you mentioned.

[janet]

Bluephoton

I'd suggest initially a major reset/reconfiguration, at a command prompt do
signal-event post-upgrade
signal-event reboot
and see if that fixes anything, if not then try analysing the problem further.

Log in as root, at the command prompt type
mc
this opens midnight commander a Xtree type file manager interface
Navigate to the directory, highlight the file and press F3 to view it, press F10 to exit

You can also do
pico -w /etc/httpd/conf/httpd.conf
Press Ctrl and x at the same time to exit
You should not make changes to this file as they will be overwritten by system events

[Bluephoton]

Thanks Mary.

I will be working on it in the evening this week.  I will try these steps and post the results.

[janet]

Bluephoton

Re your fear of losing everything, mentioned in the other thread.
What is the hard drive configuration in this server ? One drive, two drives in mirrored RAID1 or something else ?
If two drives in RAID1 then prove they are in sync with this command
cat /proc/mdstat
show us the ouput if you are unsure
Then remove one drive for safekeeping
Then proceed to recovery

You can also see the RAID1 hard disk status by logging in as admin to the admin Console and selecting the Manage disk redundancy option from the menu.
 
Alternatively if only one drive, then run a backup. Do you or do you not already have some backup routine in place ?
It's as simple as going out and buying a 1Gb USB external drive for about AUD$150
and configuring a backup to workstation (select local USB) in server manager Backup or restore panel.
You can also force a one off backup to USB from the admin Console, login as admin and select Backup to USB from the menu.

PLEASE READ THE MANUAL

I don't personally see any drama about moving the files from a users home folder to an ibay as mentioned before, and really your whole issue should be resolvable in 30 minutes, if you stay on the one task.