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.


Topics - Escorpiom

Pages: 1 [2] 3
16
I've just installed my first Zentyal 3.0 server at a client's shop. It wasn't easy but in the end all is running.
There are some minor issues however, starting with this ntp issue:

Code: [Select]
Nov 18 00:35:46 server ntpd[3723]: ntpd 4.2.6p3@1.2290-o Tue Jun  5 20:12:08 UTC 2012 (1)
Nov 18 00:35:46 server ntpd[3724]: proto: precision = 0.102 usec
Nov 18 00:35:46 server ntpd[3724]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Nov 18 00:35:46 server ntpd[3724]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING
Nov 18 00:36:09 server ntpd[4998]: process_private: failed auth mod_okay 0
Nov 18 00:36:09 server ntpd_intres[5023]: ntp_intres.request: permission denied
Nov 18 00:36:09 server ntpd[4998]: process_private: failed auth mod_okay 0
Nov 18 00:36:09 server ntpd_intres[5023]: ntp_intres.request: permission denied
Nov 18 00:36:09 server ntpd[4998]: process_private: failed auth mod_okay 0
Nov 18 00:36:09 server ntpd_intres[5023]: ntp_intres.request: permission denied

I made sure every instance of the NTP service was killed before restarting, but I cannot get rid of it. Reboot does not solve it.
Any tips would be welcome.

Cheers.

17
This morning I noticed a component update to the network configurator (Zentyal version 2.2.7) and installed it.
After saving the changes, there was no internet anymore, not on the server and not on the clients.

I restarted the server and it was obvious the firewall and network were not starting, as observed from the list of modules.
There are 4 network cards in the server, 2 external and two internal. The connection type is PPPoE.
At this moment I have started the network and firewall from the terminal and at least it enables me to post this message, but the network is still down for other clients on the network.

Please review this update because something went terribly wrong, the server is unusable at the moment. If you need more info please let me know.

Edit: The boot log, observe network and firewall not starting:
Code: [Select]
* Starting Zarafa server: zarafa-server [240G [234G[ OK ]
 * Starting Zarafa spooler: zarafa-spooler       [240G [234G[ OK ]
 * Starting Zentyal module: network              [80G [74G [31mfail [39;49m]
 * Starting Zentyal module: firewall               [80G [74G[31mfail [39;49m]
 * Starting Zentyal module: antivirus            [80G [74G[ OK ]
 * Starting Zentyal module: audit                 [80G [74G[ OK ]
 * Starting Zentyal module: ca                     [80G [74G[ OK ]
 * Starting Zentyal module: dhcp                 [80G [74G[ OK ]
 * Starting Zentyal module: dns                  [80G [74G[ OK ]
 * Starting Zentyal module: ebackup             [80G [74G[ OK ]
 * Starting Zentyal module: events               [80G [74G[ OK ]
 * Starting Zentyal module: ids                    [80G [74G[ OK ]
 * Starting Zentyal module: ipsec                [80G [74G[ OK ]
 * Starting Zentyal module: logs                 [80G [74G[ OK ]
 * Starting Zentyal module: mailfilter            [80G [74G[ OK ]
 * Starting Zentyal module: monitor             [80G [74G[ OK ]
 * Starting Zentyal module: ntp                  [80G [74G[ OK ]
 * Starting Zentyal module: openvpn           [80G [74G[ OK ]
 * Starting Zentyal module: pptp                [80G [74G[ OK ]
 * Starting Zentyal module: printers            [80G [74G[ OK ]
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
ping: unknown host vpn1.cloud.zentyal.com
 * Starting Zentyal module: remoteservices        [80G 74G[ OK ]
 * Starting Zentyal module: trafficshaping          [80G

This is a piece of the Zentyal log file when booting:
Code: [Select]
Stack:
  [/usr/share/perl5/HTML/Mason/Request.pm:127]
  [/usr/share/perl5/HTML/Mason/Request.pm:525]
2012/11/10 15:48:14 INFO> Redis.pm:766 EBox::Config::Redis::_initRedis - Starting redis server
2012/11/10 15:48:20 INFO> Base.pm:250 EBox::Module::Base::__ANON__ - Saving config for module: network
2012/11/10 15:48:25 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/11/10 15:48:30 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/11/10 15:48:31 INFO> Ldap.pm:1112 EBox::Ldap::safeConnect - LDAP reconnect successful
2012/11/10 15:48:32 ERROR> ppp-set-iface.pl:40 main::__ANON__ - Call to setRealPPPIface for eth3 failed
2012/11/10 15:48:33 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: firewall
2012/11/10 15:48:35 DEBUG> Base.pm:241 EBox::RemoteServices::Base::_queryServicesNameserver - Server vpn1.cloud.zentyal.com not found via DNS server ns.cloud.zentyal.com,127.0.0.1,8.8.4.4,8.8.8.8. Reason: SERVFAIL
2012/11/10 15:48:35 ERROR> Iptables.pm:373 EBox::Iptables::__ANON__ - Cannot contact Zentyal Cloud: Server vpn1.cloud.zentyal.com not found via DNS server ns.cloud.zentyal.com,127.0.0.1,8.8.4.4,8.8.8.8. Reason: SERVFAIL
2012/11/10 15:48:38 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: network
2012/11/10 15:48:38 ERROR> Service.pm:721 EBox::Module::Service::__ANON__ - Error restarting service: Can't call method "address" on an undefined value at /usr/share/perl5/EBox/Network.pm line 4121.
2012/11/10 15:48:38 ERROR> Lock.pm:31 EBox::Util::Lock::lock - Could not get lock for service: firewall
2012/11/10 15:48:38 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: antivirus
2012/11/10 15:48:44 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: audit
2012/11/10 15:48:44 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: ca
2012/11/10 15:48:44 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: dhcp
2012/11/10 15:48:45 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: dns
2012/11/10 15:48:46 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: ebackup
2012/11/10 15:48:46 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: events
2012/11/10 15:48:47 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: ids
2012/11/10 15:48:47 INFO> EventDaemon.pm:307 EBox::EventDaemon::_loadModules - EBox::Event::Watcher::Updates loaded from registeredEvents
2012/11/10 15:48:47 INFO> EventDaemon.pm:307 EBox::EventDaemon::_loadModules - EBox::Event::Watcher::EBackup loaded from registeredEvents
2012/11/10 15:48:47 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: ipsec
2012/11/10 15:48:47 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: logs
2012/11/10 15:48:47 INFO> EventDaemon.pm:307 EBox::EventDaemon::_loadModules - EBox::Event::Dispatcher::ControlCenter loaded from registeredDispatchers
2012/11/10 15:48:47 INFO> EventDaemon.pm:307 EBox::EventDaemon::_loadModules - EBox::Event::Dispatcher::Log loaded from registeredDispatchers
2012/11/10 15:48:47 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: mailfilter
2012/11/10 15:48:49 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: monitor
2012/11/10 15:48:50 WARN> Monitor.pm:662 EBox::Monitor::_setThresholdConf - No threshold configuration is saved since monitor watcher or events module are not enabled
2012/11/10 15:48:50 DEBUG> Base.pm:241 EBox::RemoteServices::Base::_queryServicesNameserver - Server mon.internal.cloud.zentyal.com not found via DNS server 10.200.0.4. Reason: Send error: Network is unreachable
2012/11/10 15:48:52 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: ntp
2012/11/10 15:48:53 ERROR> Sudo.pm:213 EBox::Sudo::_rootError - root command set -e
/sbin/iptables -t filter -A iexternalmodules -i tap0 -p udp --destination-port 520 -j ACCEPT
/sbin/iptables -t filter -A imodules -i tap0 -p udp --destination-port 520 -j ACCEPT
/sbin/iptables -t filter -A omodules -o tap0 -p udp --destination-port 520 -j ACCEPT
/sbin/iptables -t filter -A omodules --protocol tcp --destination vpn1.cloud.zentyal.com --destination-port 1194 -j ACCEPT
/sbin/iptables -t filter -A omodules --protocol tcp  --destination-port 80 -j ACCEPT failed.
Error output: iptables v1.4.4: host/network `vpn1.cloud.zentyal.com' not found
 Try `iptables -h' or 'iptables --help' for more information.

Command output: .
Exit value: 2
2012/11/10 15:48:53 ERROR> Iptables.pm:687 EBox::Iptables::__ANON__ - Error executing firewall rules for module openvpn
2012/11/10 15:48:54 ERROR> Sudo.pm:213 EBox::Sudo::_rootError - root command /usr/sbin/ntpdate 0.pool.ntp.org failed.
Error output: Name server cannot be used, exiting10 Nov 15:48:54 ntpdate[6555]: name server cannot be used, reason: Temporary failure in name resolution
 

Command output: .
Exit value: 1
2012/11/10 15:48:54 WARN> NTP.pm:154 EBox::NTP::__ANON__ - Couldn't execute ntpdate 0.pool.ntp.org
2012/11/10 15:48:54 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: openvpn
2012/11/10 15:48:54 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: pptp
2012/11/10 15:48:54 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: printers
2012/11/10 15:48:56 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: remoteservices
2012/11/10 15:48:56 DEBUG> Base.pm:241 EBox::RemoteServices::Base::_queryServicesNameserver - Server backup.internal.cloud.zentyal.com not found via DNS server 10.200.0.4. Reason: Send error: Network is unreachable
2012/11/10 15:48:56 ERROR> RemoteServices.pm:1590 EBox::RemoteServices::__ANON__ - Cannot contact to Zentyal Cloud: Server backup.internal.cloud.zentyal.com not found via DNS server 10.200.0.4. Reason: Send error: Network is unreachable
2012/11/10 15:48:57 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: trafficshaping
2012/11/10 15:48:57 DEBUG> TrafficShaping.pm:1104 EBox::TrafficShaping::_checkInterface - Interface ppp0 does not exist.
2012/11/10 15:48:57 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: users
2012/11/10 15:48:58 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: virt
2012/11/10 15:48:58 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: webserver
2012/11/10 15:48:59 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: asterisk
2012/11/10 15:49:00 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: bwmonitor
2012/11/10 15:49:00 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: captiveportal
2012/11/10 15:49:00 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: ftp
2012/11/10 15:49:00 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: jabber
2012/11/10 15:49:01 INFO> CaptiveDaemon.pm:233 main:: - Starting Captive Portal Daemon
2012/11/10 15:49:07 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: mail
2012/11/10 15:49:10 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: radius
2012/11/10 15:49:10 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: samba
2012/11/10 15:49:12 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: squid
2012/11/10 15:49:16 INFO> Base.pm:250 EBox::Module::Base::__ANON__ - Saving config for module: network
2012/11/10 15:49:19 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: usercorner
2012/11/10 15:49:20 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: webmail
2012/11/10 15:49:22 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: zarafa
2012/11/10 15:49:23 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: firewall
2012/11/10 15:49:24 DEBUG> Base.pm:241 EBox::RemoteServices::Base::_queryServicesNameserver - Server vpn1.cloud.zentyal.com not found via DNS server ns.cloud.zentyal.com,127.0.0.1,8.8.4.4,8.8.8.8. Reason: SERVFAIL
2012/11/10 15:49:24 ERROR> Iptables.pm:373 EBox::Iptables::__ANON__ - Cannot contact Zentyal Cloud: Server vpn1.cloud.zentyal.com not found via DNS server ns.cloud.zentyal.com,127.0.0.1,8.8.4.4,8.8.8.8. Reason: SERVFAIL
2012/11/10 15:49:26 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: apache
2012/11/10 15:49:44 ERROR> Sudo.pm:213 EBox::Sudo::_rootError - root command set -e
/sbin/iptables -t filter -A iexternalmodules -i tap0 -p udp --destination-port 520 -j ACCEPT
/sbin/iptables -t filter -A imodules -i tap0 -p udp --destination-port 520 -j ACCEPT
/sbin/iptables -t filter -A omodules -o tap0 -p udp --destination-port 520 -j ACCEPT
/sbin/iptables -t filter -A omodules --protocol tcp --destination vpn1.cloud.zentyal.com --destination-port 1194 -j ACCEPT
/sbin/iptables -t filter -A omodules --protocol tcp  --destination-port 80 -j ACCEPT failed.
Error output: iptables v1.4.4: host/network `vpn1.cloud.zentyal.com' not found
 Try `iptables -h' or 'iptables --help' for more information.

Part of the installation log, the culprit is Zentyal Network module 2.2.9
Code: [Select]
2012-11-10 05:43:58> Zentyal apt-wrapper install started
2012-11-10 05:43:58> Reading package lists...
2012-11-10 05:43:58> Building dependency tree...
2012-11-10 05:43:58> Reading state information...
2012-11-10 05:43:58> The following packages will be upgraded:
2012-11-10 05:43:58>   zentyal-network
2012-11-10 05:43:59> 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2012-11-10 05:43:59> Need to get 75.5kB of archives.
2012-11-10 05:43:59> After this operation, 0B of additional disk space will be used.
2012-11-10 05:43:59> Get:1 http://ppa.launchpad.net/zentyal/2.2/ubuntu/ lucid/main zentyal-network 2.2.9 [75.5kB]
2012-11-10 05:44:00> Fetched 75.5kB in 1s (72.9kB/s)
2012-11-10 05:44:02> (Reading database ... 139571 files and directories currently installed.)
2012-11-10 05:44:02> Preparing to replace zentyal-network 2.2.8 (using .../zentyal-network_2.2.9_all.deb) ...
2012-11-10 05:44:02> Unpacking replacement zentyal-network ...
2012-11-10 05:44:02> Setting up zentyal-network (2.2.9) ...
2012-11-10 05:44:15>  * Restarting Zentyal module: network
2012-11-10 05:44:15>    ...done.
2012-11-10 05:44:15>
2012-11-10 05:44:15> Processing triggers for zentyal-core ...
2012-11-10 05:44:16>  * Restarting Zentyal module: apache
2012-11-10 05:44:16>    ...done.
2012-11-10 05:44:18>  * Restarting Zentyal module: logs
2012-11-10 05:44:18>    ...done.
2012-11-10 05:44:20>  * Restarting Zentyal module: events
2012-11-10 05:44:20>    ...done.
2012-11-10 05:44:21> Zentyal apt-wrapper install finished

Cheers.

18
I'm a little confused  :)
running Zentyal with Samba as a non-PDC, goal is to do basic filesharing.
On the first page, "general settings" the "domain name" parameter has to be specified.
My organization has a domain name, it's like "mycomputernetwork.com" that allows presence on the web.

So, logically I filled out that domain name in the Samba "general" configuration page. And that is where the trouble starts.
Looking in the file /var/log/samba/nmbd, this error appears:

Code: [Select]
name_to_nstring: workgroup name MYCOMPUTERNETWORK.COM is too long. Truncating to MYCOMPUTERNETWO
Investigating further, it became clear that the "domain name" cannot contain more than 15 characters, hence the error.
Looking at the Zentyal documentation, it is stated:

Code: [Select]
The domain is set to work within the Windows local network
So my question would be:
- Do I need to change my existing domain name to something less than 15 characters, or
- Is the domain name field actually referring to the "workgroup" name since it is used on the local network?

I find this a little bit confusing.

Cheers.

 

19
Dutch / Voorlopig programma van de Zentyal Summit 2012.
« on: September 11, 2012, 12:59:01 pm »
Onderstaand persbericht ter info.

5 september 2012

(Zaragoza, Spanje)
Zentyal S.L, ontwikkelaar van de Zentyal Linux Small Business Server, heeft vandaag het voorlopige programma voor de Zentyal Summit 2012 aangekondigd, dat zal plaatsvinden op 4 en 5 oktober in Zaragoza, Spanje. Gebaseerd op de ervaring en feedback van de extreem populaire summit van vorig jaar, gaat het programma dit jaar verder met het verstrekken van cutting-edge content voor de behoeften van IT-ondersteuning aan service providers en IT-beheerders geïnteresseerd in Linux-gebaseerde IT-infrastructuur management oplossingen voor kleine en middelgrote bedrijven (MKB/KMO).

De summit begint op donderdag 4 oktober met een toespraak van Tom Henriksson, Partner bij Open Ocean Capital. Tijdens zijn toespraak "De sleutel om categorie-winnende open source bedrijven te herkennen en te toetsen" geeft hij inzicht in wat er nodig is voor open source start-ups om succesvol te worden. Open Oceaan, de eerste grote eigenaar van MySQL AB, is een toonaangevend vroeg-stadium venture capital bedrijf, met nadruk op Europese start-ups waar het gaat om de inzet van een gebruikers gemeenschap van het open source business model.

Tijdens de twee dagen van het evenement, geven open source software fabrikanten zoals Canonical, ontwikkelaar van het populaire Ubuntu, besturingssysteem, en Zarafa, ontwikkelaar van het Zarafa e-mail-en samenwerkingsplatform, samen met Zentyal een reeks van zowel commerciële presentaties als technische workshops. Het zal mogelijk zijn om te leren over desktop en server migratie naar Linux-gebaseerde systemen, hoe de hardware te kiezen of om de infrastructuur te integreren met user-level toepassingen, of welke voordelen Samba 4 en single-sign-on hebben voor het IT-infrastructuur management in het MKB, om er maar een paar te noemen.

Naast advies van fabrikanten, zullen de deelnemers ook de kans krijgen om te leren hoe IT-ondersteuning en service providers, zoals Leucotron, Neodoo of Calat, hun eigen service portefeuilles bouwen op basis van Linux en open source oplossingen.  Aan de andere kant, zal de Community trac, gehouden op vrijdag 5 oktober, inzicht geven in de rol van de gemeenschap achter Zentyal als een open source project en zal het ook de kans geven om ideeën voor te stellen en uit te breiden voor de roadmap van de volgende versie van Zentyal server.

Er hoeft geen inschrijfgeld betaald te worden voor deelname aan het evenement, maar het aantal plaatsen is beperkt, dus een spoedige inschrijving wordt ten zeerste aanbevolen. Zowel het programma als inschrijvingsformulier zijn te vinden op de summit website op: http://summit.zentyal.com.
De Zentyal Summit 2012 wordt gesponsord door de Zaragoza gemeenteraad en Milla Digital, Canonical, Zarafa, Neodoo en Nationaal Referentiecentrum voor ICT gebaseerd op OSS (CENATIC).

Aanvullende informatie:

Zentyal Summit 2012 Programma:
http://events.zentyal.com/zentyal-summit-2012/program-2012/ (downloaden in . pdf )

Zentyal Summit 2012 Inschrijvingen:
http://events.zentyal.com/zentyal-summit-2012/register-2012/

Over Zentyal (www.zentyal.com)
Zentyal, ontwikkelaar van de Linux Small Business Server met dezelfde naam, biedt kleine en middelgrote bedrijven een enterprise-niveau, betaalbare en eenvoudig te gebruiken netwerkinfrastructuur.  Door het gebruik van Zentyal server en de cloud-gebaseerde diensten, zijn kleine en middelgrote bedrijven in staat om de betrouwbaarheid en de veiligheid van hun computernetwerk te verbeteren en om hun IT-investeringen en operationele kosten te verlagen.
De Zentyal server ontwikkeling is gestart begin 2004, en op dit moment is het het open source alternatief voor Windows Small Business Server.  Zentyal server wordt veel gebruikt in kleine en middelgrote bedrijven ongeacht de sector, industrie of locatie, maar ook bij de overheid en in de educatieve sector.

20
The syslog is filled with these messages:

Code: [Select]
named[4579]: error (network unreachable) resolving 'user.ipcam.hk/A/IN': 2001:500:14:6046:ad::1#53
named[4579]: error (network unreachable) resolving 'user.ipcam.hk/A/IN': 2001:dc0:1:0:4777::140#53
named[4579]: error (network unreachable) resolving 'user.ipcam.hk/A/IN': 2405:3000:3:60::21#53
named[4579]: error (network unreachable) resolving 'user.ipcam.hk/A/IN': 2607:f140:ffff:fffe::3#53

After checking with my provider, it appears that both my adsl modem and the provider's network are not ipv6 capable.
It should be easy to disable ipv6 in bind9, by adding -4 to /etc/default/bind9
This is how it looks now:

Code: [Select]
# run resolvconf?
RESOLVCONF=yes

# startup options for the server
OPTIONS="-4 -u bind"

Restarted bind from the console and all was well...at least that's how it should be.
The errors just keep coming while ipv6 is disabled, why is bind still trying to resolve ipv6 when there is a specific directive set
to use only ipv4?

I read about adding some lines to sysctl.conf:

Code: [Select]
# IPv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

But before something gets borked, can someone push me in the right direction?

Cheers.
 


21
There are reports of similar issues on the forum, but at the moment I don't know what is the status of this issue.
Zentyal Cloud is still not working, it shows connected on the admin page but the VPN log states:
Code: [Select]
Tue Jun  5 20:54:13 2012 TCP: connect to [AF_INET]92.243.6.103:1194 failed, will try again in 5 seconds: Connection timed out
It's best to add some images to this post.
I've been unsubscribing and subscribing my server over and over again, sometimes it works for two days but it always drops offline after a while.
The cloud module was updated some days ago, and now it always shows connected but it does not reflect the real connection status.






Still hoping for a solution, some day.

Cheers.

22
Dutch / Richtlijnen voor het aanmaken van berichten of onderwerpen.
« on: May 26, 2012, 01:50:32 pm »
Deze instructies komen oorspronkelijk uit het Engelse forumdeel, voor sommigen is het misschien wat makkelijker te volgen in het Nederlands.
Met dank aan Oceanwatcher. 

Welkom bij de Nederlandse Zentyal gemeenschap!
Iedereen helpt hier op vrijwillige basis, we antwoorden als we iets weten over het onderwerp en als de tijd het toelaat. Wellicht kun je zelf ook actief helpen.

Om eventuele problemen snel op te kunnen lossen, zijn er enkele dingen die je kunt doen voordat je hier een bericht post.
Als je eenmaal besluit om te posten, zijn er een aantal gegevens die je zowiezo dient te vermelden.

De zoekfunctie.
--------------
Allereerst: Zoeken. Het is goed mogelijk dat je niet de enige bent met het probleem, dus maak gebruik van de zoekfunctie. Soms kan het lastig zijn om de juiste woorden te vinden (niet iedereen spreekt Engels of Spaans), maar probeer het gewoon. Je kunt dan in je bericht vermelden waar je naar gezocht hebt.

Upgraden.
----------
Zorg ervoor dat je installatie up to date is. De ontwikkelaars van Zentyal werken elke dag aan de software en eventuele bugs worden zo snel mogelijk verholpen.
Upgraden doe je door deze commando's op de commandline in te geven:

Code: [Select]
sudo apt-get update
sudo apt-get upgrade


Posten.
--------
Mocht het euvel niet verholpen zijn, maak dan een bericht met een korte omschrijving van het probleem als onderwerp.
Vermijd kreten zoals "Help!" of "Ik heb een probleem...". Gebruik geen voorvoegsels, behalve dan [OPGELOST] als de kwestie opgelost is. Hou het kort en bondig.

Zentyal versie.
--------------
Vermeld altijd de Zentyal versie waarmee je werkt, evenals de versie van het Ubuntu besturingssysteem.
De huidige stabiele versie is Zentyal 2.2, de beta versie 2.3 wordt later dit jaar Zentyal 3.0.
Het is mogelijk dat de beta versie nog enkele bugs heeft, hou daar rekening mee als je een keuze moet maken tussen Zentyal 2.2 of Zentyal 2.3.   

Functie en situatie.
------------------
Is het een productie server (wordt actief gebruikt) of is het een configuratie die enkel voor testen gebuikt wordt?
Is Zentyal op een PC geïnstalleerd, of draait het in een virtuele machine zoals VirtualBox enz.?
Hoe is de Zentyal machine op het Internet aangesloten?
Is deze server de gateway naar het internet voor je netwerk?

Versies van de Zentyal modules.
------------------------------
Er zijn nog een paar andere dingen die je ook kunt vermelden.
Geef dit commando op de commandline in en plak het resultaat in het bericht:

Code: [Select]
dpkg -l | grep "zentyal-"

Debug mode.
-----------
Je kunt Zentyal ook in "debug mode" laten draaien, als het probleem dan opnieuw optreedt kun je de logs bij je bericht voegen zodat we er naar kunnen kijken.
Zo doe je dit: (start een console via SSH of geef deze commandos in een console op de server):

Code: [Select]
sudo nano /etc/zentyal/zentyal.conf
Verander "debug = no" in "debug = yes" en sla het bestand op.

Code: [Select]
sudo /etc/init.d/zentyal apache restart

Probeer om het probleem weer op te laten treden. Herhaal de procedure die Zentyal liet crashen of stoppen.  Vergeet niet om deze procedure ook in je bericht te vermelden.
We hebben dit nodig om zelf ook te kunnen zien waar het fout gaat.

Post je zentyal.log
------------------
Je kunt het bestand hier vinden:
Code: [Select]
/var/log/zentyal/zentyal.log
Ga naar de website:
Code: [Select]
http://paste.ubuntu.com/en plak de inhoud van het bestand hier. Voeg dan de link toe aan je bericht.

Het onderwerp als "Opgelost" betitelen.
----------------------------------------
Als het probleem opgelost is kun je de titel van het onderwerp veranderen en er [Opgelost] voor zetten.
Je doet dit door naar het eerste bericht in het onderwerp te gaan en op de knop "Modify" te klikken. Je kunt dan de titel veranderen.
Dit helpt iedereen om juist die onderwerpen te vinden waar mogelijk reeds een oplossing voor het probleem gegeven is.
In het geval dat er nog geen [Opgelost] voor staat, kan dit betekenen dat het probleem nog niet is opgelost en dat verdere hulp nodig is.


23
It's been a while, Zentyal is working great. I have a minor issue with tracert and perhaps other members might have noticed it?
When doing a trace route from a PC on the local network, the hops that are part of our internal network take a long time to resolve.
From reading on the net, I understand it is a problem with reverse lookup. Doing a nslookup yields:

Code: [Select]
C:\Documents and Settings\Escorpiom>nslookup
DNS request timed out.
    timeout was 2 seconds.
*** Can't find server name for address 192.168.0.2: Timed out
*** Default servers are not available
Default Server:  UnKnown
Address:  192.168.0.2
>

This weird behaviour started only a few days ago. Pinging internal (or external) IP's directly is no problem.
If I use the switch /d for the tracert command, all is well (obviously)
The OS is windows XP, DNS server IP is the Zentyal box.
I also tried setting the DNS server to Google DNS, the result is the same.
Executing tracert from the zentyal gui itself is OK, so the issue might be some recent update.
I'm open to suggestions, but most of all I would like to know why it never happened before?

Cheers.


24
Recently, when rebooting the Zentyal server, I noticed the IPSec service is not starting. It can't be started from the admin page.
As a result, the server can not connect to Zentyal cloud.
To resolve this issue, it's necessary to open a terminal as root and type:
Code: [Select]
service ipsec stop
And the resulting message states that there was an "orphaned pluto.pid" and it was removed.
Typing:
Code: [Select]
service ipsec starteffectively restarts the IPSec service and it also shows as started on the admin page.

The annoying part of it all is that the cloud subscription does not work anymore and the server has to be "unsubscribed" and after that subscribed again.
This procedure has to be repeated at every reboot.
I read about the valid subdomain name and I'm sure it is valid, no weird characters in the name.

Is there anything that can be done to solve this behavior?

Cheers.


25
Squid proxy is behaving very strange lately. I included the log, perhaps someone has seen these lines?

Code: [Select]
2011/12/31 16:30:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:35:02| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 16:35:10| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:35:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 16:35:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:40:02| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 16:40:10| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:40:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 16:40:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:45:02| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 16:45:09| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:45:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 16:45:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:50:02| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 16:50:10| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:50:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 16:50:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:55:02| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 16:55:10| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 16:55:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 16:55:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:00:03| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 17:00:10| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:00:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 17:00:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:05:02| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 17:05:10| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:05:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 17:05:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:05:36| WARNING: All url_rewriter processes are busy.
2011/12/31 17:05:36| WARNING: up to 6 pending requests queued
2011/12/31 17:06:14| WARNING: All url_rewriter processes are busy.
2011/12/31 17:06:14| WARNING: up to 13 pending requests queued
2011/12/31 17:06:14| Consider increasing the number of url_rewriter processes to at least 18 in your config file.
2011/12/31 17:10:03| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 17:10:10| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:10:12| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 17:10:17| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:15:02| CACHEMGR: <unknown>@127.0.0.1 requesting 'info'
2011/12/31 17:15:09| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:15:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'storedir'
2011/12/31 17:15:16| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
2011/12/31 17:16:35| WARNING: All url_rewriter processes are busy.
2011/12/31 17:16:35| WARNING: up to 5 pending requests queued
2011/12/31 17:17:05| WARNING: All url_rewriter processes are busy.
2011/12/31 17:17:05| WARNING: up to 23 pending requests queued
2011/12/31 17:17:05| storeDirWriteCleanLogs: Starting...
2011/12/31 17:17:05| WARNING: Closing open FD   24
2011/12/31 17:17:05| commSetEvents: epoll_ctl(EPOLL_CTL_DEL): failed on fd=24: (1) Operation not permitted
2011/12/31 17:17:05|     65536 entries written so far.
2011/12/31 17:17:05|    131072 entries written so far.
2011/12/31 17:17:05|    196608 entries written so far.
2011/12/31 17:17:05|    262144 entries written so far.
2011/12/31 17:17:05|   Finished.  Wrote 278520 entries.
2011/12/31 17:17:05|   Took 0.1 seconds (3905380.2 entries/sec).
FATAL: Too many queued url_rewriter requests (15 on 5)
Squid Cache (Version 2.7.STABLE7): Terminated abnormally.

It seems that url_rewriter requests are the cause of the crash. But I don't know if the "CACHEMGR: <unknown>@127.0.0.1 requesting" lines have something to do with it.
I have shut down the Apache webserver and Zoneminder but nevertheless the messages are still appearing and squid might be crashing again any moment.

Cheers.

26
Installation and Upgrades / Zentyal Cloud - Basic subscription problem.
« on: November 29, 2011, 03:09:06 am »
My server disconnected from Zentyal Cloud about one week ago, without any reason.
The VPN log showed that it couldn't connect to the public IP address (timed out). So I pinged the public IP and got the echo.
Searching the relevant topics I found the advice to remove the server's basic subscription and to subscribe the server again.
Then I got this error:
Code: [Select]
An internal error has occurred. This is most probably a bug, relevant information can be found in the logs. Please look for the details in the /var/log/zentyal/zentyal.log file and take a minute to submit a bug report so we can fix the issue as soon as possible.
The Zentyal log showed this:

Code: [Select]
2011/11/28 20:57:34 INFO> Base.pm:228 EBox::Module::Base::save - Restarting service for module: openvpn
2011/11/28 20:57:35 ERROR> Sudo.pm:213 EBox::Sudo::_rootError - root command apt-key del ebox-qa failed.
Error output: gpg: key "ebox-qa" not found: eof
 gpg: ebox-qa: delete key failed: eof

Command output: .
Exit value: 2
2011/11/28 20:57:35 ERROR> Subscription.pm:776 EBox::RemoteServices::Subscription::__ANON__ - Removal of apt-key ebox-qa failed. Check it and if it exists remove it manually
2011/11/28 20:57:36 INFO> Subscription.pm:802 EBox::RemoteServices::Subscription::_removeDDNSConf - DynDNS is using other service, not modifying
2011/11/28 20:57:56 WARN> SOAPClient.pm:84 EBox::RemoteServices::SOAPClient::instance - Doing connection to web service: urn:EBox/Services/RegisteredEBoxList without credentials to https://92.243.29.209/soap
2011/11/28 20:58:03 INFO> Subscription.pm:590 EBox::RemoteServices::Subscription::_setDDNSConf - DynDNS is already in used, so not using Zentyal Cloud service
2011/11/28 20:58:05 ERROR> Sudo.pm:213 EBox::Sudo::_rootError - root command cp '/var/lib/zentyal/conf/remoteservices/subscription/anubis/FE3272DB150B8378.pem' '/var/lib/zentyal/tmp/certificate_path' failed.
Error output: cp: cannot stat `/var/lib/zentyal/conf/remoteservices/subscription/anubis/FE3272DB150B8378.pem': No such file or directory

Command output: .
Exit value: 1

I have some problem with the certificate that is non-existent, so it seems. How can I resolve this problem?

Cheers.

Edit:
Amazing, I actually repaired something myself as opposed to borking my server every now and then.
After the error, what I did was removing the server subscription from Zentyal itself, > save modules. OK.
Then I subscribed the server again, got the message "Subscription data retrieved successfully".
Save modules and check cloud status > Working!

This post might be of interest for those troubleshooting Zentyal cloud issues.

27
Installation and Upgrades / Adding exceptions to the Adzapper script.
« on: November 24, 2011, 07:34:19 pm »
Better to tackle this issue right now before someone else is looking all over...

Today one of my users complained about not being able to see the photos on some website. He said that somewhere else the photos were loading just fine.
After visiting this site:
Code: [Select]
http://www.amarillasinternet.comand conducting a search like "restaurantes", no images were displayed on the right side of the screen.
Opening the foto gallery yielded the same result.
I knew instantly that it was the Adzapper playing up, but adding the sites address to the exception list (Dansguardian) didn't solve anything.

After poking around in my server I found the script here:
Code: [Select]
/usr/bin/adzapper 

A little down the list there are a few lines starting with "PASS", those are the sites that will NOT be zapped so I just maintained the same format and added
amarillasinternet to the list.
After restarting the proxy all was well.
I don't know if this will "stick" after an update. In that case it could be helpful to know how we can create static exception lists.

You have to take care with the cache, sometimes you need to clear the browser cache to have all the stuff come up again.
Hope this eventually saves people from searching all over.

Cheers.

28
I the process of finishing my new Zentyal 2.2 setup I came across several little anoyances.
After changing something in Zentyal, when saving, the firewall takes quite a long time to save.
It just sits there for a minute before all other stuff saves.
This is the corresponding error in the logs:

Code: [Select]
ERROR> Lock.pm:31 EBox::Util::Lock::lock - Could not get lock for service: firewall
2011/11/19 03:27:11 INFO> CaptiveDaemon.pm:233 main:: - Starting Captive Portal Daemon
2011/11/19 03:27:11 ERROR> Lock.pm:31 EBox::Util::Lock::lock - Could not get lock for service: firewall
2011/11/19 03:27:12 INFO> CaptiveDaemon.pm:233 main:: - Starting Captive Portal Daemon
2011/11/19 03:27:12 ERROR> Lock.pm:31 EBox::Util::Lock::lock - Could not get lock for service: firewall
2011/11/19 03:27:13 INFO> CaptiveDaemon.pm:233 main:: - Starting Captive Portal Daemon

Perhaps I've got an idea how this happened. Wanting to block Facebook, I created a network object with al of Facebook IP's inside.
There were about 4 ranges and those made up for really a lot of IP's.
When putting the block rule in the firewall with destination the Facebook IP's, it probably was too much because saving took nearly 15 minutes
and even the Internet connection went down.
Seeing this was an impossible situation, I quickly removed the block rule from the firewall.
Saving the configuration went a lot faster, but still not as fast as before the incident.
 
The question is, could there be some left overs in the firewall config? Does Zentyal really delete the rules or is it like "disabled"?
How can I troubleshoot this situation?

Cheers.

29
In the Squid logs this message appears:

Code: [Select]
WARNING: All url_rewriter processes are busy.
WARNING: up to 15 pending requests queued
Consider increasing the number of url_rewriter processes to at least 20 in your config file.

I looked in squid.conf.mas and at line 31 it states:

Code: [Select]
$urlRewriteProgram => undef
How can I define the urlRewriteProgram and subsequently, get rid of the errors?

Cheers.

Add some extra info:
I found  this on the web, it seems that on Linux the package can be compiled (or should I say "build") with these options
Code: [Select]
Squid 2.6: --with-maxfd=65536
Squid 3.x: --with-filedescriptors=65536
replace 65536 with the number of rewriters you want.

This is annoying because everytime it happens, it stalls pages loading and the delay is noticeable.
I suspect that our Zentyal Squid wasn't compiled with this option. I would really like some feedback from the devs, I'm willing to open a bugreport in the tracker if it's necessary.

30
Installation and Upgrades / Error creating new users.
« on: November 17, 2011, 10:35:21 pm »
The last issue to report for today in 2.2 is a Samba bug on a 2.2 fresh install.
When creating new users, click on "add" and some error pops ups that it can't create the directories. Result: User dir is created but no profile!
As a workaround we can create the directory structure by hand, after that users can be created without errors.

Create folder
Code: [Select]
/home/samba
In that folder create 3 subfolders:
Code: [Select]
groups
netlogon
profiles

Create users as planned.
Cheers.

Pages: 1 [2] 3