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.
Pages: [1]
1
German / Re: Zentyal Backup läuft nicht mehr
« on: December 04, 2012, 12:24:55 am »
Die Lösung fand ich hier:
http://forum.zentyal.org/index.php/topic,12954.msg54619.html#msg54619
Es gibt einen Patch für die Datei "duplicity-wrapper".
Der Fehler hat mit den "locales" Einstellungen zu tun.
Gruss,
EntireNet
http://forum.zentyal.org/index.php/topic,12954.msg54619.html#msg54619
Es gibt einen Patch für die Datei "duplicity-wrapper".
Der Fehler hat mit den "locales" Einstellungen zu tun.
Gruss,
EntireNet
2
German / [gelöst] Zentyal Backup läuft nicht mehr
« on: December 03, 2012, 02:03:07 am »
Hallo zusammen,
das Backup auf einem Ubuntu 12.04 LTS Server mit Zentyal 3.0 läuft nicht mehr.
Bis zu einem Update am 25.11.2012 lief alles, danach in der Nacht wurde kein Backup mehr durchgeführt. In den Logfiles steht folgendes:
2012/12/02 05:00:01 INFO> Redis.pm:509 EBox::Config::Redis::_initRedis - Starting redis server
2012/12/02 05:00:39 WARN> backup-tool:244 main::_adjustType - Incremental backup requested but there are not full backups. Switching to full backup mode
2012/12/02 05:01:01 INFO> Backup.pm:735 EBox::Backup::makeBackup - Backing up configuration
2012/12/02 05:01:08 ERROR> Sudo.pm:233 EBox::Sudo::_rootError - root command start 'samba4' failed.
2012/12/02 05:01:08 ERROR> Backup.pm:148 EBox::Backup::__ANON__ - root command start 'samba4' failed.
2012/12/02 05:01:08 ERROR> EBackup.pm:338 EBox::EBackup::__ANON__ - Configuration backup failed: root command start 'samba4' failed.
2012/12/02 05:01:08 INFO> backup-tool:342 main::__ANON__ - Backing up files to destination: try 1
2012/12/02 08:09:58 INFO> backup-tool:554 main::__ANON__ - Backup process finished successfuly
Am Ende heisst es das Backup sei erfolgreich gewesen, aber in der Liste der zuvor erfolgten Backups taucht nach dem 25.11.2012 nichts mehr auf.
Das Backup wird auf einen FTP Server gesichert. Ich kann dort mit den konfigurierten Zugangsdaten ohne Probleme einloggen. Dort ist auch genug Speicher frei. Leider sind die Details in der zentyal.log nicht sehr umfangreich.
"Incremental backup requested but there are not full backups. Switching to full backup mode" sagt mir das die vorhandenen inkrementellen Backups nicht erkannt werden, und damit niemmt das Unheil wohl seinen Lauf.
Kennt sich jemand besser mit dem Backup Prozess aus?
Gruss,
EntireNet
das Backup auf einem Ubuntu 12.04 LTS Server mit Zentyal 3.0 läuft nicht mehr.
Bis zu einem Update am 25.11.2012 lief alles, danach in der Nacht wurde kein Backup mehr durchgeführt. In den Logfiles steht folgendes:
2012/12/02 05:00:01 INFO> Redis.pm:509 EBox::Config::Redis::_initRedis - Starting redis server
2012/12/02 05:00:39 WARN> backup-tool:244 main::_adjustType - Incremental backup requested but there are not full backups. Switching to full backup mode
2012/12/02 05:01:01 INFO> Backup.pm:735 EBox::Backup::makeBackup - Backing up configuration
2012/12/02 05:01:08 ERROR> Sudo.pm:233 EBox::Sudo::_rootError - root command start 'samba4' failed.
2012/12/02 05:01:08 ERROR> Backup.pm:148 EBox::Backup::__ANON__ - root command start 'samba4' failed.
2012/12/02 05:01:08 ERROR> EBackup.pm:338 EBox::EBackup::__ANON__ - Configuration backup failed: root command start 'samba4' failed.
2012/12/02 05:01:08 INFO> backup-tool:342 main::__ANON__ - Backing up files to destination: try 1
2012/12/02 08:09:58 INFO> backup-tool:554 main::__ANON__ - Backup process finished successfuly
Am Ende heisst es das Backup sei erfolgreich gewesen, aber in der Liste der zuvor erfolgten Backups taucht nach dem 25.11.2012 nichts mehr auf.
Das Backup wird auf einen FTP Server gesichert. Ich kann dort mit den konfigurierten Zugangsdaten ohne Probleme einloggen. Dort ist auch genug Speicher frei. Leider sind die Details in der zentyal.log nicht sehr umfangreich.
"Incremental backup requested but there are not full backups. Switching to full backup mode" sagt mir das die vorhandenen inkrementellen Backups nicht erkannt werden, und damit niemmt das Unheil wohl seinen Lauf.
Kennt sich jemand besser mit dem Backup Prozess aus?
Gruss,
EntireNet
3
Installation and Upgrades / [SOLVED] Re: Zarafa IMAP and SASLAUTH for SMTP Authentication
« on: August 04, 2011, 04:19:47 pm »
Hi again,
Problem is solved!
STARTTLS expected the users email address as username, not the LDAP username. This seems to be something which is configured in dovecot i believe.
In my case now, IMAP uses the LDAP username and for SMTP the email adress is used for username.
Yours,
entirenet
Problem is solved!
STARTTLS expected the users email address as username, not the LDAP username. This seems to be something which is configured in dovecot i believe.
In my case now, IMAP uses the LDAP username and for SMTP the email adress is used for username.
Yours,
entirenet
4
Installation and Upgrades / Zarafa IMAP and SASLAUTH for SMTP Authentication
« on: August 04, 2011, 03:27:49 pm »
Hello everybody,
i have a problem with authenticating smtp usage via STARTTLS using rimap as mechanism against the Zarafa IMAP Gateway.
In the gateway.log i see no authentication attempt (loglevel 5).
In the mail.log is see this error:
SASL LOGIN authentication failed: UGFzc3dvcmQ6
UGFzc3dvcmQ6 is base64 decoded = Password --> not the used password to login, no just the word itself.
With debug_peer_list and postfix smtpd loglevel 4 you can see what is reported back to the client:
535 5.7.8 Error: authentication failed: UGFzc3dvcmQ6
CLI testing seems ok:
testsaslauthd -u username -p password -f /var/spool/postfix/var/run/saslauthd/mux
0: OK "Success."
I checked many howtos and other forums about that "SASL LOGIN authentication failed: UGFzc3dvcmQ6" error message. Unfortunately this error is reported on varios configuration problems.
I don't use the dovecot pop/imap service, only the Zarafa Gateway. The default postfix configuration uses smtpd_sasl_type = dovecot. Maybe this leads to problems when the dovecot services are not used?
Any hints or somebody has/had similar problems with sasl?
Yours,
entirenet
i have a problem with authenticating smtp usage via STARTTLS using rimap as mechanism against the Zarafa IMAP Gateway.
In the gateway.log i see no authentication attempt (loglevel 5).
In the mail.log is see this error:
SASL LOGIN authentication failed: UGFzc3dvcmQ6
UGFzc3dvcmQ6 is base64 decoded = Password --> not the used password to login, no just the word itself.
With debug_peer_list and postfix smtpd loglevel 4 you can see what is reported back to the client:
535 5.7.8 Error: authentication failed: UGFzc3dvcmQ6
CLI testing seems ok:
testsaslauthd -u username -p password -f /var/spool/postfix/var/run/saslauthd/mux
0: OK "Success."
I checked many howtos and other forums about that "SASL LOGIN authentication failed: UGFzc3dvcmQ6" error message. Unfortunately this error is reported on varios configuration problems.
I don't use the dovecot pop/imap service, only the Zarafa Gateway. The default postfix configuration uses smtpd_sasl_type = dovecot. Maybe this leads to problems when the dovecot services are not used?
Any hints or somebody has/had similar problems with sasl?
Yours,
entirenet
5
Installation and Upgrades / Re: Zentyal GUI not working after shutdown of fresh Installation
« on: June 06, 2011, 02:43:51 am »Hi there,
i found the problem by myself. I changed the ebox apache port to 8443 wich was already used by zarafa-ical service.
I stopped the zarafa-ical service and did a restart of the ebox apache module, then i was able to log into the GUI again. There i changed the ebox apache port to 8444 which is not in use (checked before with netstat -lp).
Problem solved!
Yours,
Entirenet
6
Installation and Upgrades / Re: Web Admin
« on: June 06, 2011, 02:06:27 am »Hi,
i have the same problem after restarting the server after a fresh install. Do you get "bad request" error messages too?
Yours,
Entirenet
7
Installation and Upgrades / [Solved] Zentyal GUI not working after shutdown of fresh Installation
« on: June 05, 2011, 09:58:40 pm »
Hi there,
after a ahutdown my fresh installed Zentyal server is back on normal service, but the Zentyal GUI is not working any more.
I configured tcp port 8443 and now i receive" Bad Request".
I had to shutdown the server 'cause of a very heavy thunderstorm last night. The server was shutdown with poweroff command via shell, but this was within a running zentyal backup schedule. Is there any context on the unfinished backup and GUI troubles i have now?
I'm not very familiar with Zentyal at this point, so i don't know where to check whats going wrong with the GUI.
I need your help.
Yours,
Entirenet
after a ahutdown my fresh installed Zentyal server is back on normal service, but the Zentyal GUI is not working any more.
I configured tcp port 8443 and now i receive" Bad Request".
I had to shutdown the server 'cause of a very heavy thunderstorm last night. The server was shutdown with poweroff command via shell, but this was within a running zentyal backup schedule. Is there any context on the unfinished backup and GUI troubles i have now?
I'm not very familiar with Zentyal at this point, so i don't know where to check whats going wrong with the GUI.
I need your help.
Yours,
Entirenet
8
Installation and Upgrades / Zentyal | Zarafa - Store attachments outside of the database
« on: June 03, 2011, 11:10:59 pm »Hi everybody,
i know how to store attachments outside of the dabase on a zarafa standalone installation.
When i configure zentyal with zarafa for storing attachments outside of the db, the /etc/zarafa/server.cfg always will be overwritten by the defaults configured in zentyal.
How can i change this?
Yours,
Entirenet
Pages: [1]