Page 1 of 1
No Language Defined after changing vesta server time?
Posted: Wed Aug 26, 2015 12:16 pm
by darkdeva92
My server time in the vesta panel was set to New York so I went in an changed it to London.
It then logged me out and whenever I try to login I get "No Language Defined"
Could someone please help me? I have to much data and users on the panel to do a fresh install!
What would be causing this problem?
Please help!
Thanks
Re: No Language Defined after changing vesta server time?
Posted: Thu Aug 27, 2015 7:12 am
by skurudo
Show output, please.
The error occurs when disk space outs
Re: No Language Defined after changing vesta server time?
Posted: Thu Aug 27, 2015 11:10 am
by darkdeva92
This is what i'm getting
Code: Select all
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 40G 9.9G 28G 27% /
tmpfs 1004M 0 1004M 0% /dev/shm
Code: Select all
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/vda1 2621440 95860 2525580 4% /
tmpfs 256803 1 256802 1% /dev/shm
Code: Select all
total used free shared buffers cached
Mem: 2006 1915 90 1 107 1188
-/+ buffers/cache: 619 1386
Swap: 0 0 0
Re: No Language Defined after changing vesta server time?
Posted: Thu Aug 27, 2015 12:30 pm
by skurudo
darkdeva92, Two options:
- Try this: remove everything from the /tmp folder.
- Broken sudo:
viewtopic.php?f=10&t=8349&p=27113#p27113
Re: No Language Defined after changing vesta server time?
Posted: Sat Aug 29, 2015 12:02 am
by SCelik
Re: No Language Defined after changing vesta server time?
Posted: Mon Aug 31, 2015 7:02 am
by skurudo
SCelik, nice remark!
There was topic lately about quota problem for admin user:
viewtopic.php?f=40&t=9037&p=30983#p31032
Re: No Language Defined after changing vesta server time?
Posted: Mon Aug 31, 2015 9:19 pm
by SCelik
skurudo, there is a bug with quota system. When you set quota on user, softlimit is set correctly but hardlimit is always 40.000. At least on Centos 6.7
I don't know if it's related with Vesta or Centos..
Re: No Language Defined after changing vesta server time?
Posted: Mon Jun 20, 2016 7:34 pm
by skurudo
Popular reason - you don't have free disk space or inode. Check with commands:
But error can be with disk quota.. to fix this there is option:
Code: Select all
nano /usr/local/vesta/data/users/admin/user.conf
For votes and ideas:
https://bugs.vestacp.com/issues/261