Messages

1

Installation and Upgrades / Unknown error at EBox::Asterisk::Extensions::firstFreeExtension Sizelimit exceed

« on: August 09, 2015, 07:26:01 am »

Need a help ....

When i try to create users on zentiyal bellow error appearing...

Unknown error at EBox::Asterisk::Extensions::firstFreeExtension Sizelimit exceeded...

    Unknown error at EBox::Asterisk::Extensions::firstFreeExtension Sizelimit exceeded at /usr/share/perl5/EBox/Ldap.pm line 701
    EBox::Ldap::_errorOnLdap('Net::LDAP::Search=HASH(0xbc225b30)', 'HASH(0xbab57058)') called at /usr/share/perl5/EBox/Ldap.pm line 341
    EBox::Ldap::search('EBox::Ldap=HASH(0xb98cc998)', 'HASH(0xbab57058)') called at /usr/share/perl5/EBox/Asterisk/Extensions.pm line 146
    EBox::Asterisk::Extensions::firstFreeExtension('EBox::Asterisk::Extensions=HASH(0xbc234808)') called at /usr/share/perl5/EBox/AsteriskLdapUser.pm line 94
    EBox::AsteriskLdapUser::_addUser('EBox::AsteriskLdapUser=HASH(0xbc234348)', 'farookf', 'asdfgh') called at /usr/share/perl5/EBox/UsersAndGroups.pm line 908
    EBox::UsersAndGroups::initUser('EBox::UsersAndGroups=HASH(0xb9770c18)', 'farookf', 'asdfgh') called at /usr/share/perl5/EBox/UsersAndGroups.pm line 1117
    EBox::UsersAndGroups::addUser('EBox::UsersAndGroups=HASH(0xb9770c18)', 'HASH(0xb9970708)') called at /usr/share/perl5/EBox/CGI/UsersAndGroups/AddUser.pm line 77
    EBox::CGI::UsersAndGroups::AddUser::_process('EBox::CGI::UsersAndGroups::AddUser=HASH(0xb9361d20)') called at /usr/share/perl5/EBox/CGI/Base.pm line 275
    EBox::CGI::Base::run('EBox::CGI::UsersAndGroups::AddUser=HASH(0xb9361d20)') called at /usr/share/perl5/EBox/CGI/Run.pm line 129
    EBox::CGI::Run::run('EBox::CGI::Run', 'UsersAndGroups/AddUser', 'EBox') called at /usr/share/zentyal/cgi/ebox.cgi line 34
    ModPerl::ROOT::ModPerl::Registry::usr_share_zentyal_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xb939f1b8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
    eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
    ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xb936df10)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
    ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xb936df10)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
    ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xb939f1b8)') called at -e line 0
    eval {...} called at -e line 0

2

Installation and Upgrades / Re: On zentyal 2.2 antivirus is not running

« on: October 01, 2011, 09:56:45 am »

no errors on zentyal.log but when i sudo /etc/init.d/zentyal antivirus restart  service is running now.
thats means every time if i restart the server i have to restart antivirus?

3

Installation and Upgrades / On zentyal 2.2 antivirus is not running

« on: September 25, 2011, 09:25:11 am »

Hi There,
I have install zentyal 2.2 but antivirus is not running, its says on dashboard  "stopped" i had same issue on 2.0 also but i manage get i work after i update the antivirus on "zentyal components" after my 4th installation.
is anybody have a solution for this? and
why this happening on zental 2.0      " Status:    The antivirus database has not been updated since the module was enabled"     

4

Installation and Upgrades / Re: The file system /dev/mapper/mail-root, mounted on /, has no space left

« on: August 12, 2011, 07:27:56 am »

Hi vhinzsanchez,
Thank you for the information, i will follow your steps but this is a running email server will this crash?
 

Check the other posts.

http://forum.zentyal.org/index.php?topic=6055.0

Just lookout for the 6th message..posted by zolf.  Do not issue rm -rf on /var/log.  I do not know what has gotten into me (maybe confused..I did something similar a while back but not on /var/log itself, maybe folders deep, that is why I freed up space with no problem) i did it...I'm now problematic.  I can reinstall but the hassle of the nice setup I previously made will be wasted.

please help.

i did the following

cd /var/log

rm -rf *

and then ran df,so now my /dev/mapper/ubuntu-home has changed from 100% to 63% of used space.but i dont get the zentyal interface to login,i get the terminal window to work with only.
please help

Pay close attention to the solutions posted by Escorpiom, organetic and aryana.haribawa.  Those made sense.

I can't post a quick solution to the problem, but I can give some tips to prevent it.
My root was full a few days ago. It was mainly because of Squid, but logfiles also can cause the problem. My server did not start anymore.

If you are going to install Zentyall, DO NOT use the automated harddisk setup. You'll end up with a very small root (in my case 7GB) that fills up in no-time and the home gets all the space you'll likely never use.
One day your server will freeze, and at reboot it just won't start.
Zentyal is using lvm2 (Logical Volume Manager 2) for the automated hd setup.
If you see /dev/mapper/ it means that your setup uses the LVM2 scheme.

In that case what you can do is resize the root volume, that's where all the important stuff is.
Zentyal LVM2 setup only uses 3 volumes:
- root = all the important stuff
- swap = only used as a kind of swap memory, not for storage
- home = for user files and samba stuff
The /boot volume is NOT part of the LVM2 scheme, you can see it like /dev/sda1.
Don't be confused about hda and sda, it just IDE harddisk or SATA / SCSI harddisk.

Leave swap alone.
Check how much space is used for /home. You have to take some space from /home  and give it to /root.
You'll have to shrink /home, after that expand /root to use that free space.

Now the bad news:
1. You will have to learn the LVM2 partitioning scheme. Search on the web.
2. Resizing is done from the Ubuntu live CD WITHOUT mounting the volumes.
3. Each resize operation has two steps, resizing the volume AND the file system. If you do it wrong, you will LOOSE your /home volume and will have to recreate it (I screwed it).
4. Do NOT use Gparted. It doesn't support LVM2 yet.
5. Do not use the graphical interface "system-config-lvm" as it will wipe out the whole VG.

In some cases you might just start over all again and choose manual hd setup.
I find it a mayor flaw that Zentyal/Ubuntu automatic setup uses such a smal root. 

Some commands you can use from commandline:
df lists the filesystems and used/available space. Start here to see what is full.
pvdisplay lists the physical volume, you can see this as a partition
vgdisplay lists details about the volume group like name, allocated/available space. A volume group can hold one or more partitions, they can sit on different hd's.
lvdisplay lists the logical volumes inside the volume group. On a default install, /root, /swap and /home will be listed.

What can you do to avoid filling your /root?
1. Relocate the Squid cache. I had the cache set to 6GB while my /root was 7GB. Stupid but I learned.
2. Logfiles are being renamed first, then compressed. You might try and delete the gzipped log files, but Zentyal itself has an option to purge logs. Anyway, it has been recommended to rotate logs more aggressively.   

Should we better not use LVM2 partitioning scheme but the normal one instead?
No. I do think that LVM2, once mastered, will be way more easier to manage volumes. It has a learning curve but in the long run it makes adding hd's a snap. Imagine just adding a new harddisk to your system and extending your root volume to use that space?
 
I'm surprised that there is so little input from Zentyal staff on these kind of problems. Sometimes we need just a little guidance, it's hard enough already coming from Windows.

Cheers.

First off,
Partitioning and other harddisk stuff is basic Ubuntu stuff and has little to do with Zentyal itself.
I think that's why Zentyall staff doesn't support these kind of issues.
Although I understand their motivation, it does create a huge gap for people that are new to Linux and decide to try Zentyal as a first step.
Zentyal will only be accessible to the more experienced Linux folks who already know their basics.

So if we want to bridge that gap we will have to do it ourself. There is not much of a community here (judging by the amount of unanswered posts) so we have to build one 

I do believe Zentyal to be a great product, and if the next update takes care of the speed issues I could become a happy user.
In the meanwhile, I'll try to help as much as possible at my n00b level.

From what I have gathered, the root fills up because:
- excessive log files
- Squid cache (located at /var/spool/squid)
- Zentyal backups
 
Note that the default cache size is set at 128MB, so Squid cache will only become a problem if you change it manually to something rather big.
For the log files, you can delete the Gzipped logs safely.

As for the resizing, I only dug in to the LVM method a few days ago. At this point I simply haven't got enough information to write a "step-by-step-resizing-manual".
If you decide to set up Zentyal from scratch, in that case I would recommend:
- Choose LVM. It's much more easier in the long rung
- Depending on your harddisk size, choose a large /root. I would do 30GB - 40GB
- Be carefull with the size of your Squid cache. If you choose several gigabytes they WILL be populated in days so take note of of your /root size.
- Do not worry about /home, if you should need more space it's easy to add or relocate.
- For swap, choose two times your mem size. For example, you have 4GB of RAM, swap can be 8GB.
- /boot is rather small and doesn't change from what I've noticed. It's about 195MB with 32MB used on my system. 
 
Other more experienced users may opt to put /var on their own volume. Above is only meant as a n00b guide.
If you have something to add or if something is wrong, please comment. Others will be thankful.

Cheers.

I do believe that I've managed to find a solution (at least temporary) for this nasty problem that affects all production servers out there.

I have a home volume group of around 442GB, so what I've made was to take out 30GB of /home and gave it to /root

I've made the following procedures:

1 - Boot the Zentyal Server with the official installation CD
2 - select the option the option to repair the computer with the instaled Zentyal
3 - after selecting the network card and time zone, DO NOT mount a volume
4 - Select the option to execute a console
5 - type the following commands,

first, check your server name and size of the home volume group typing the following command:

# lvdisplay

then, after checking names and sizes

# e2fsck /dev/your-server-name/home
# resize2fs -f /dev/your-server-name/home 412G
# lvreduce -L412G /dev/your-server-name/home
# lvextend -L30G /dev/your-server-name/root
# e2fsck /dev/your-server-name/root
# resize2fs /dev/your-server-name/root

please notice that I've used 412G but you can use another size to define your home partition.
Just don't forget that the space you'll earn for root is the diference between what you had and what you choose here.

Maybe someone can make a script with these commands, asking the user what size to give to root.
and auto-detecting the name of the computer. This would be the preferrable way.

As for my part, at least, the server is now working ok after all.

Please take this as a first approach to the problem, and develop it more.

The Zentyal team could make a script like this run at the end of the installation, so this problem would never happen again.

I'm just worried that the root size keeps expanding... Will this bug eat the whole 30GB ?!!

Hi, have you solved this problem? If Not, I have written a doc on how to resize Zentyal Root LVM Partition safely. This problem is very common.

Andre
http://forum.zentyal.org/index.php?action=dlattach;topic=6055.0;attach=697

5

Installation and Upgrades / The file system /dev/mapper/mail-root, mounted on /, has no space left

« on: August 11, 2011, 12:48:10 pm »

Edited by Christian:

Duplicate post.
No need to post same topic in multiple sections 

----------------------------------------------


I have more space on dev/mapper/mail-home, how can i use this space to mail-root?

Thanks in advance

--- Volume group ---
VG Name mail
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 74.26 GiB
PE Size 4.00 MiB
Total PE 19011
Alloc PE / Size 19011 / 74.26 GiB
Free PE / Size 0 / 0
VG UUID UpM12d-WqPl-0Q6v-U9Td-BZY2-5BgX-rPj6qK
*********************************************

/dev/mapper/mail-root 6.5G 5.9G 239M 97% /
none 496M 208K 496M 1% /dev
none 501M 0 501M 0% /dev/shm
none 501M 128K 501M 1% /var/run
none 501M 0 501M 0% /var/lock
none 501M 0 501M 0% /lib/init/rw
/dev/sda1 2 28M 17M 200M 8% /boot
/dev/mapper/mail-home 64G 433M 61G 1% /home

6

Installation and Upgrades / The file system /dev/mapper/mail-root, mounted on /, has no space left

« on: August 11, 2011, 12:37:32 pm »

I have more space on dev/mapper/mail-home, how can i use this space to mail-root?

Thanks in advance

--- Volume group ---
VG Name mail
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 74.26 GiB
PE Size 4.00 MiB
Total PE 19011
Alloc PE / Size 19011 / 74.26 GiB
Free PE / Size 0 / 0
VG UUID UpM12d-WqPl-0Q6v-U9Td-BZY2-5BgX-rPj6qK
*********************************************

/dev/mapper/mail-root 6.5G 5.9G 239M 97% /
none 496M 208K 496M 1% /dev
none 501M 0 501M 0% /dev/shm
none 501M 128K 501M 1% /var/run
none 501M 0 501M 0% /var/lock
none 501M 0 501M 0% /lib/init/rw
/dev/sda1 2 28M 17M 200M 8% /boot
/dev/mapper/mail-home 64G 433M 61G 1% /home