Virtualmin won't install, fatal error, ubuntu 10.10

7 posts / 0 new
Topic locked
Last post
#1 Wed, 11/24/2010 - 19:45
Pezmc

Virtualmin won't install, fatal error, ubuntu 10.10

Curently writing this from my phone as Internet down. When I run the instal.sg script as root on ubuntu 10.10.

=Summary of the end of the log= Download apt.conf Install keys Download GPGKEY Virtualmin Download GPGKEY webmin Ok Ok Removing debiak webmin Removing apache Reading Installing dependencies... Reading package list Building dep tree Reading state information FATAL error Cannot continue

This is trying to install on a 64bit x336 imb server with ubuntu server fresh install (installed just before this command).

Anyone know what's goig wrong? Log doesn't seem that useful!

Thanks,

Wed, 11/24/2010 - 20:19
andreychek

Howdy,

Virtualmin isn't actually supported on Ubuntu 10.10... it can be made to work, but it may require a decent bit of manual configuration :-)

We recommend using the LTS release, Ubuntu 10.04. That's a more suitable distribution for servers, and when using it, everything should work for you out of the box when you run the install.sh script.

-Eric

Thu, 11/25/2010 - 08:26
Pezmc

Thanks for the info eric, changed back to 10.04 and now it is working!

Might as well add to this thread rather than starting another (unless I get no replies xD)

Is it possible to stop users being able to leave (go higher up than) their home directory? I created a vserver with what I thought was only ssh access but they can view other users files etc...

Thu, 11/25/2010 - 09:01
andreychek

Is it possible to stop users being able to leave (go higher up than) their home directory? I created a vserver with what I thought was only ssh access but they can view other users files

SSH users aren't locked into their home directories, though they can only see files that they have appropriate permission to see.

While FTP allows you to lock the users into a homedir, it's ultimately not possible to prevent a user from being able to see a file they have permission to see (for example, they could just install a PHP-based file browser and see those same files).

-Eric

Thu, 11/25/2010 - 09:31
Locutus

@Pezmc: If they can not only see the other users' directories, but actually browse into them and read files, you can fix that by removing the "world-readable" flag from those directories, like so:

chmod -R a-rx /home/directoryinquestion

(Pay attention when entering this command, since due to the -R it operates recursively, and you don't want to mess up the access rights for your root file system. ;) )

Apache will still have access, as long as you keep the group-readable flag, since Apache gets added to the vserver owner's group upon creation.

Fri, 11/26/2010 - 09:38
Pezmc

Just to check my understanding, something like chmod 640 would be appropriate as then the "world" cannot see each users files, but the owner can read and write, and apache can read?

Many thanks for your posts,

Fri, 11/26/2010 - 10:32
Locutus

Yeah, 640 is read and write for owner, read for group and nothing for the rest.

Pay attention to also set the Execute bit for directories if you want read access, since that means "can traverse into directory".

Topic locked