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 - mehargags

Pages: [1]
1
Now  I get stuck at the DNS -- when I ENABLE DNS -- the Webadmin gui gives "504 Gateway Times-out" while I CAN STILL SSH
What can be the problem ?

2
Well,
I solved network thing... was rather funny. After you set the Network interface to your Public IP and Enable Network module, you will be locked up (being on a single IP/NIC). All you have to do is reboot the server/VPS to regain control.

I was restlessly wiping off the VPS after the lockup... somethings are ridiculously easy to overlook.

Further testing the next things....

3
Sorry,
had been out of touch and I'm back towards this exercise. I did make an Accept rule yet I get locked out at the moment I configure an IP address on the Network interface!

4
No, I can't SSH in... that is the problem, I get locked out.
I have to wash the VPS, and install zentyal all over again, which eats up 10-15 mins everytime.

any remedies ?

5
Im too  ;D
mugging my heads up for the last 3 days! posted here https://forum.zentyal.org/index.php/topic,23996.0.html, have got the response but its s pretty standardized reply, not something specific to VPS with public IP.

let me know if you come across a solution :}

6
Hi royceb,

You are right about the firewall getting me locked up. However I have 2 different VPS's from different providers, the behavior is different.
On VPS1 I just put the Public IP 50.xxx.xxx.xx4/255.255.255.0 on the NIC which is my public IP and the network gets enabled. Interesteingly, I have all modules set to "ON" on this Vps with just Firewall being OFF.

on the second VPS2 (the problem one here), I could put 2xx.1xx.1xx.xx5/255.255.255.0 and enable the newtork, however, the moment I was Mail and other modules to set on, they push the firewall to be SET ON and I'm locked out.

Can you explain the different behaviour of Zentyal on these 2 VPSs?  I sincerely think its a small thing but I'm not able to tackle it.

7
http://scavansystems.com/test/zentyal4/Zentyal-install-log.htm
I'm installing Zentyal 4 to be an Openchange/sogo server for hosting around 200 mailboxes spread across 3-4 different domains.

I've been struggling What to set in the network settings, I read many posts about this but all end up incomplete, can't guess if they could resolve or not their issues.

Will try to put up as straight, pardon my ignorance as I'm new to all this and learning fast.

1.   I have a 6GB/300GB VPS with 2 IPv4 Addresses. Installed Ubuntu 14.04 minimal
2.   If I IFCONFIG My server it outputs (real IPs removed)

venet0:0  Link   inet addr:2xx.1xx.1xx.xx5  P-t-P: 2xx.1xx.1xx.xx5  Bcast: 2xx.1xx.1xx.xx5  Mask:255.255.255.255

venet0:1  Link  inet addr: 2xx.1xx.1xx.xx6  P-t-P: 2xx.1xx.1xx.xx6  Bcast: 2xx.1xx.1xx.xx6  Mask:255.255.255.255

3.   I install Zentyal, login to webadmin Choose Mail and Groupware only  install
4.   Skip Network configuration & configure interfaces
 

 

5.   Put a domain name for my server--> Next
 

6.   I land in my Dashboard,  I see Network in disabled. I presume I need Network interface/IPs set, DNS service installed and running to enable OpenChange to work properly.
Here onwards I seek some help in what do I put in my network configuration.

If I put 2xx.1xx.1xx.xx5  /255.255.255.0 to my venet0 and press save changes, I’m locked out of my box, and can’t even SSH. I read amnay have this problem, but no thread posted a resolution clearly.

Can you please help me resolve this very first step? I ask questions in the picture below for a better understanding.

 


Thanks alot...

8
Resolved it -- loos like a known bug on deb/ubu systems.

had to use :

Code: [Select]
# apt-get --reinstall install bsdutils
and then proceed with # apt-get install zentyal

9
Hi,
I'm trying to install this on a FRESH VPS : 6GB RAM/6GB Swap/4Cores, a clean install of Ubuntu 14.04 x64, but even after 7-8 tries the installation would inevitably error out at
Quote
dpkg: error processing package mysql-server
Quoting some last lines before the install fails
Code: [Select]
Unpacking at (3.1.14-1ubuntu1) ...
Processing triggers for install-info (5.2.0.dfsg.1-2) ...
Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
Setting up libdbi-perl (1.630-1) ...
Setting up libmysqlclient18:amd64 (5.5.40-0ubuntu0.14.04.1) ...
Setting up libdbd-mysql-perl (4.025-1) ...
Setting up libterm-readkey-perl (2.31-1) ...
Setting up mysql-client-core-5.5 (5.5.40-0ubuntu0.14.04.1) ...
Setting up mysql-client-5.5 (5.5.40-0ubuntu0.14.04.1) ...
Setting up libaio1:amd64 (0.3.109-4) ...
Setting up mysql-server-core-5.5 (5.5.40-0ubuntu0.14.04.1) ...
Setting up mysql-server-5.5 (5.5.40-0ubuntu0.14.04.1) ...
/var/lib/dpkg/info/mysql-server-5.5.postinst: line 146: logger: command not found
ATTENTION: An error has occured. More info is in the syslog!
/var/lib/dpkg/info/mysql-server-5.5.postinst: line 236: logger: command not found
dpkg: error processing package mysql-server-5.5 (--configure):
 subprocess installed post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.5; however:
  Package mysql-server-5.5 is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
Errors were encountered while processing:
 mysql-server-5.5
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

tail /var/log/syslog
Code: [Select]
Nov 27 17:00:16 hst rsyslogd: imklog: error reading kernel log - shutting down: Bad file descriptor
Nov 27 17:00:16 hst rsyslogd: message repeated 498 times: [imklog: error reading kernel log - shutting down: Bad file descriptor]
Nov 27 17:00:22 hst rsyslogd-2177: rsyslogd[internal_messages]: 5218007 messages lost due to rate-limiting
Nov 27 17:00:22 hst rsyslogd: imklog: error reading kernel log - shutting down: Bad file descriptor
Nov 27 17:00:22 hst rsyslogd: message repeated 498 times: [imklog: error reading kernel log - shutting down: Bad file descriptor]
Nov 27 17:00:28 hst rsyslogd-2177: rsyslogd[internal_messages]: 5334465 messages lost due to rate-limiting
Nov 27 17:00:28 hst rsyslogd: imklog: error reading kernel log - shutting down: Bad file descriptor
Nov 27 17:00:28 hst rsyslogd: message repeated 498 times: [imklog: error reading kernel log - shutting down: Bad file descriptor]
Nov 27 17:00:34 hst rsyslogd-2177: rsyslogd[internal_messages]: 5379631 messages lost due to rate-limiting
Nov 27 17:00:34 hst rsyslogd: imklog: error reading kernel log - shutting down: Bad file descriptor

please point me in right direction...
thanks alot.

Pages: [1]