Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - davidt

Pages: [1] 2
1
Installation and Upgrades / Bootloop Issue when Login to System
« on: June 05, 2018, 08:59:39 am »
Hi All,

I am looking for some assistance with my system, recently it has come up with the following error:

No space left on device at /usr/share/perl5/Log/Log4perl/Appender/File.pm line 268

or the full one:

Cannot write to '/var/log/zentyal/zentyal.log': Operation not permitted at /usr/share/perl5/Log/Log4perl/Appender/File.pm line 268

I cannot get to the GUI or cannot login to the system via the desktop.

I have truncated the log files, and deleted old log files and still no luck.

This is starting to annoy me as it happens about once every two weeks and I have to go on a deleting spree to try and at least get the system up and running, but then it doesnt take long for this to happen again, and I have more than 70GB of free space on the drive as well.

Any advice in fixing this up it would be much appreciated.

(PS) I noticed that in the bug tracker this was a known issues with version 3 and in early versions of 4, it would seem this bug/issue has transposed over into the current version again.

Desperate for some help!

Cheers,

David.

2
Installation and Upgrades / Re: [Problem] Zentyal 5.0 service fails.
« on: March 06, 2018, 11:21:06 am »
This seems like the same bug others and myself are seeing with the mail services stopping on its own accord.

 :(

Cheers,

David.

3
Installation and Upgrades / Re: SMTP service down after update
« on: March 06, 2018, 11:16:41 am »
Hi Mate,

I have this same problem, it started out as just SMTP and I could restart it, now it is all the mail services stopping and I cannot see why.

The only time I know about it is when e-mails stop comming through after an hour or so, and then I check and I have to click restart on the services, then it goes good for about a few days and then they slowly start to stop again.

Nothing else is effected, only the mails ervices.

I notcied this got worse after an update, though I am not sure what got updated last time as Zentyal does not show any historical updates.

I hope they can fix this in a new update, it is very annoying when e-mails stop flowing.

Cheers,

David.

4
OK so I finally got a fresh install to work right at the 16th attempt.

Such a simple problem would cause a big issue and make a fresh install unusable.

Simple cure was to SSH into the server, stop the ClamAV service, then update the database, once that is completed (Can take upwards of 45 minutes as their server is slow) you then restart the service.

The Zentyal system wont run the mail filtering until an update is done, but it would also seem that this the same wether or not you are running it under Zentyal or not, however it since it does not update during a fresh install, it leaves the system in an unstable state.

Procedure to get around this problem:

* Do the fresh install and wait till you get to the GUI - Complete the install of all the modules

* Wait till the admin panel loads up fully - you will be greeted with about 19 updates, please make sure you do these before doing anything else otherwise you run the risk of the DNS module becoming corrupted, and then never being able to restart it again

* Once updates of security and system updates are completed, reboot the system

* Once the system is rebooted proceed to SSH into the system (Alternatives is to sudo su if you don't want to keep running sudo on each thing)
- sudo service clamav-freshclam stop
- sudo freshclam  (Wait for it to complete an update, this can take a while so don't cancel it or stop it)
- sudo service clamav-freshclam start

* Log back into the admin panel and begin setting everything up

NOTE: It can take a while for the Zentyal admin panel to show you that the Antivirus services are running, until then, you may get e-mail coming through as **UN-CHECKED**, but be assured that it will come alive again.

NOTE-2: I don't know if this methods works with upgrades as my last attempt at upgrading resulted in me losing everything so I had to venture down the pathway of doing a fresh install.

Cheers,

David.

5
Installation and Upgrades / Re: Fresh Install of 5.0.9 Antivirus Wont Work
« on: September 24, 2017, 03:11:55 pm »
OK up to attempt number 9 now....

This time I am going to try it without installing firewall or Jabber and see what happens.

Since the errors appear to be relating to Jabber and also associated to the firewall, I can only see how that fairs up.

Going onto about 37 hours now trying to get this to work... If anyone else offered ActiveSync I would have given up a long time ago, it is the only thing that is keeping me sticking around and being patient with this.

6
Installation and Upgrades / Re: Fresh Install of 5.0.9 Antivirus Wont Work
« on: September 24, 2017, 02:09:03 pm »
Hi Bert,

I feel your pain mate :(

This is now my 5th attempt at getting this latest version working, and I keep getting the same issue.

2017/09/24 21:58:19 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 21:58:19 INFO> Base.pm:231 EBox::Module::Base::save - Restarting service for module: logs
2017/09/24 21:58:30 INFO> GlobalImpl.pm:723 EBox::GlobalImpl::saveAllModules - Changes saved successfully
2017/09/24 21:58:32 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 21:58:50 INFO> Service.pm:958 EBox::Module::Service::restartService - Restarting service for module: antivirus
2017/09/24 21:58:51 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 21:59:10 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 21:59:42 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:00:12 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:00:37 INFO> Service.pm:958 EBox::Module::Service::restartService - Restarting service for module: antivirus
2017/09/24 22:00:39 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:01:11 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:01:41 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:02:11 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:02:41 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:03:11 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:03:41 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:04:18 INFO> GlobalImpl.pm:625 EBox::GlobalImpl::saveAllModules - Saving config and restarting services: firewall jabber
2017/09/24 22:04:18 INFO> Base.pm:231 EBox::Module::Base::save - Restarting service for module: firewall
2017/09/24 22:04:18 INFO> Base.pm:231 EBox::Module::Base::save - Restarting service for module: jabber
2017/09/24 22:04:20 INFO> LDAP.pm:246 EBox::Module::LDAP::_sendSchemaUpdate - Sending schema update:
2017/09/24 22:04:20 INFO> LDAP.pm:246 EBox::Module::LDAP::_sendSchemaUpdate - Sending schema update:
2017/09/24 22:04:20 INFO> LDAP.pm:304 EBox::Module::LDAP::waitForLDAPObject - Waiting for schema object present: CN=jabberUid,CN=Schema,CN=Configuration,DC=thetrads,DC=com
2017/09/24 22:04:20 INFO> LDAP.pm:304 EBox::Module::LDAP::waitForLDAPObject - Waiting for schema object present: CN=jabberAdmin,CN=Schema,CN=Configuration,DC=thetrads,DC=com
2017/09/24 22:04:21 INFO> LDAP.pm:304 EBox::Module::LDAP::waitForLDAPObject - Waiting for schema object present: CN=userJabberAccount,CN=Schema,CN=Configuration,DC=thetrads,DC=com
2017/09/24 22:04:21 INFO> GlobalImpl.pm:723 EBox::GlobalImpl::saveAllModules - Changes saved successfully
2017/09/24 22:04:36 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:04:46 INFO> Service.pm:958 EBox::Module::Service::restartService - Restarting service for module: antivirus
2017/09/24 22:04:48 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2017/09/24 22:05:20 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.

No matter what I do, I always have the same problem  :'( :'( :'( :'( :'(

Antivirus   Stopped

I just cannot get a stable clean install of 5.0.9.

I would highly recommend that no one upgrades production systems to this new version.

Cheers,

David.

7
Installation and Upgrades / Re: Frsh Install of 5.0.9 Antivirus Wont Work
« on: September 23, 2017, 03:13:51 pm »
Hi lalpi,

I appreciate your advice and I am trying everything I can to get the system to work.

Right now I have to turn off in modules, Antivirus and Mail filter, they just wont work.

I will give everything you suggested and hope it helps :)

Cheers,

David.

8
Installation and Upgrades / Re: Upgrade from 5.0.8 to 5.0.9 Fails
« on: September 23, 2017, 03:03:29 pm »
Hi Lalpi,
Appreciate your response but it was not recoverable and per the other posts that followed that, a new build was done.

The problem is that the new build even failed heavily, I cannot turn on mail filtering, or antivirus, and other services refuse to work as well.

I still stick by my comment that 5.0.9 has major issues.


Cheers,

David.

9
Installation and Upgrades / Re: Upgrade from 5.0.8 to 5.0.9 Fails
« on: September 20, 2017, 08:29:06 am »
Hi Bert,

Yeah Zentyal 5.0.9 has big issues and I would encourage anyone to not upgrade to it and to avoid it for now.

basically you wont get Mail Filter or Antivirus working, and if you try then Sama will crash as well.

I have now done 4 seperate installs from scratch and can reproduce the issues every time.

Cheers,

David.

10
Hi Community,

After being forced to freshly install the latest version 5.0.9 from 5.0.8, I am now not able to get antivirus working:

Antivirus   Stopped

No matter how many times I click the restart button or when it changes to start, it just remains on stopped.

Everything else has started working jut not that.

I have disabled the module and re-enabled it and that still does not work.

Is there anyway I can get it forced to come on via command line or something? Every single e-mail now is coming through as ***UNCHECKED*** or they are not coming through at all.

I have to say, after spending near on 18 hours trying to resolve the massive crash that took place when upgrading from 5.0.8 to the latest version, I learnt a lot about mail servers, given the continual problems with Zentyal, Axigen is looking more and more promising... You may not get ActiveSync with the free version, but the rest of it is very polished, and I think I might consider paying.

If anyone has any suggestions on how to get antivirus to work, it would be greatly appreciated.


Cheers,

David.

11
Installation and Upgrades / Re: Upgrade from 5.0.8 to 5.0.9 Fails
« on: September 18, 2017, 03:59:10 pm »
Hi Julio,

I appreciate all your help that you have provided, sadly it wont progress no matter, I have to put it down to everything is lost.

I have decided I will do a fresh install and work it out from there, I have been trying other systems whilst trying to resolve this tonight and will work out what I am going to do tomorrow.

Been trying to resolve this now for 14 hours, there comes a time when one has to cut their losses.

Thanks for your help  it was appreciated.

12
Installation and Upgrades / Re: Upgrade from 5.0.8 to 5.0.9 Fails
« on: September 18, 2017, 03:51:04 pm »
Hi Julio,

Tried as you suggested, sorry it just gets stuck on the same thing...

root@zentyal:/tmp# sudo dpkg -i zentyal-core_5.0.9_all.deb
(Reading database ... 78189 files and directories currently installed.)
Preparing to unpack zentyal-core_5.0.9_all.deb ...
Unpacking zentyal-core (5.0.9) over (5.0.9) ...
Setting up zentyal-core (5.0.9) ...

It wont progress past that.

13
Installation and Upgrades / Re: Upgrade from 5.0.8 to 5.0.9 Fails
« on: September 18, 2017, 03:15:08 pm »
Hi Julio,

root@zentyal:/tmp# apt install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up zentyal-core (5.0.9) ...


It just gets stuck there and doesn't move, and  I cannot repair the package either for some reason, it just wont work.

14
Installation and Upgrades / Re: Upgrade from 5.0.8 to 5.0.9 Fails
« on: September 18, 2017, 03:01:08 pm »
Hi Julio,

Thanks for the advice, I get this error message.

root@zentyal:/tmp# dpkg -i zentyal-dns_5.0.3_all.deb
Selecting previously unselected package zentyal-dns.
(Reading database ... 78189 files and directories currently installed.)
Preparing to unpack zentyal-dns_5.0.3_all.deb ...
Unpacking zentyal-dns (5.0.3) over (5.0.3) ...
dpkg: dependency problems prevent configuration of zentyal-dns:
 zentyal-dns depends on zentyal-core (>= 5.0); however:
  Package zentyal-core is not configured yet.
 zentyal-dns depends on zentyal-core (<< 5.1); however:
  Package zentyal-core is not configured yet.

dpkg: error processing package zentyal-dns (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 zentyal-dns

I think it is totally stuffed, I should have not done the update and should have left things as they were :(

15
Installation and Upgrades / Re: Upgrade from 5.0.8 to 5.0.9 Fails
« on: September 18, 2017, 02:14:00 pm »
Hi Julio,

So this is what happens when I try to do as you suggest  :'(

root@zentyal:/home/itadmin# sudo apt install --reinstall zentyal-dns
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

Pages: [1] 2