Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators
Reload this Page Memcached Does Not Start

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-26-2011, 08:02 PM
Advanced Member
  
Posts: 189
Default Memcached Does Not Start
Here's the background: migrating from FOSS 7.1.3 32 bit on SLES10 to FOSS 7.1.3 64 bit on SLES11. I have been following:
Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki
to the "T". On step "7" of "For all versions:" (zmcontrol start) i get this:
Starting ldap...Done.
Starting zmconfigd...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting memcached...Failed.
Starting memcached.../opt/zimbra/bin/zmmemcachedctl: line 65: /opt/zimbra/memcached/bin/memcached: No such file or directory
failed.


Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.

A zmcontrol status shows this:
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Stopped
zmmailboxdctl is not running.
memcached Stopped
memcached is not running.
mta Running
snmp Running
spell Running
stats Running
zmconfigd Running


Now, i understand that in order for this to work, the new 64 bit server MUST be configured exactly like the 32 bit server. I verified on the 32 bit server that memcached IS installed. On the 64 bit server memcached is NOT installed. Is there a way to install memchaced on the 64 bit server after the initial install without breaking anything/everything and would this cause mailboxd not to start?
Reply With Quote
  #2 (permalink)  
Old 12-26-2011, 11:07 PM
Zimbra Consultant & Moderator
  
Posts: 20,314
Default
You should not be running memcached on a single server installation (which I assume this is). Run the following commands to check what's installed:

Code:
zmprov gs `zmhostname` | grep zimbraServiceEnabled
zmprov gs `zmhostname` | grep zimbraServiceInstalled
Disable the it with the following:

Code:
zmprov ms `zmhostname` -zimbraServiceEnabled memcached
zmprov ms `zmhostname` -zimbraServiceInstalled memcached[
You should restart zimbra after making those changes.
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 12-27-2011, 04:42 AM
Advanced Member
  
Posts: 189
Default
Quote:
Originally Posted by phoenix View Post
You should not be running memcached on a single server installation (which I assume this is).
Right, single server installation. It is just that the 32 bit server has been upgraded since 4.5.8 (?) to 7.1.3; so back then, memchaced installed by default (?) and now you are asked if you want to install memcache

Quote:
Run the following commands to check what's installed:
Not what i want to see when running commands:
Code:
zmprov gs `zmhostname` | grep zimbraServiceEnabled
[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
[] INFO: Retrying request
ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
zimbra@mail:~> zmprov gs `zmhostname` | grep zimbraServiceInstalled
[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
[] INFO: Retrying request
ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
Logically, i think the problem carries over from the 32 bit server which DID have memchaced. It seems logical that one of the config files from the 32 bit server (which is now on a 64 bit server without memchaced) is calling for memcached, hence the error as memcached is NOT installed.
I just thought, can i uninstall memcached from the 32 bit server and then follow the migrating 32 bit to 64 bit wiki doc?
Reply With Quote
  #4 (permalink)  
Old 12-27-2011, 04:49 AM
Zimbra Consultant & Moderator
  
Posts: 20,314
Default
Quote:
Originally Posted by carnold View Post
Logically, i think the problem carries over from the 32 bit server which DID have memchaced. It seems logical that one of the config files from the 32 bit server (which is now on a 64 bit server without memchaced) is calling for memcached, hence the error as memcached is NOT installed.
Was Zimbra actually running when you ran that command?

Quote:
Originally Posted by carnold View Post
I just thought, can i uninstall memcached from the 32 bit server and then follow the migrating 32 bit to 64 bit wiki doc?
Yes, you can certainly do that.
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 12-27-2011, 05:08 AM
Advanced Member
  
Posts: 189
Default
[QUOTE=phoenix;233695]Was Zimbra actually running when you ran that command?[/QUOTE

Running on the 64 bit server? If that is the question the answer is no because it will not start due to the memcached error. Zimbra was running on the 32 bit server when i started the migrating process.
In what file should i be looking for specific errors in regards to this issue? Zmmailboxd.out shows this but i am not sure if it is related:
Code:
1    INFO  [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
Total time for which application threads were stopped: 0.0001920 seconds
Total time for which application threads were stopped: 0.0003160 seconds
Zimbra server reserving server socket port=110 bindaddr=192.168.124.3 ssl=false
Zimbra server reserving server socket port=995 bindaddr=192.168.124.3 ssl=true
Fatal error: exception while binding to ports
java.net.SocketException: Unbound server sockets not implemented
	at javax.net.ServerSocketFactory.createServerSocket(ServerSocketFactory.java:80)
	at com.zimbra.common.util.NetUtil.newBoundServerSocket(NetUtil.java:95)
	at com.zimbra.common.util.NetUtil.bindServerSocket(NetUtil.java:163)
	at com.zimbra.common.util.NetUtil.bindSslTcpServerSocket(NetUtil.java:54)
	at com.zimbra.common.handlers.PrivilegedHandler.openPorts(PrivilegedHandler.java:82)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.mortbay.xml.XmlConfiguration.call(XmlConfiguration.java:542)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:252)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
	at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.mortbay.start.Main.invokeMain(Main.java:194)
	at org.mortbay.start.Main.start(Main.java:534)
	at org.mortbay.start.Main.start(Main.java:441)
	at org.mortbay.start.Main.main(Main.java:119)
Heap
 par new generation   total 217536K, used 15499K [0x00000000bcc00000, 0x00000000cb800000, 0x00000000cb800000)
  eden space 193408K,   8% used [0x00000000bcc00000, 0x00000000bdb22da0, 0x00000000c88e0000)
  from space 24128K,   0% used [0x00000000c88e0000, 0x00000000c88e0000, 0x00000000ca070000)
  to   space 24128K,   0% used [0x00000000ca070000, 0x00000000ca070000, 0x00000000cb800000)
 concurrent mark-sweep generation total 728064K, used 0K [0x00000000cb800000, 0x00000000f7f00000, 0x00000000f8000000)
 concurrent-mark-sweep perm gen total 131072K, used 9155K [0x00000000f8000000, 0x0000000100000000, 0x0000000100000000)
A simple netstat -pan does not show any 110 or 995 ports as being used:
Code:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
tcp        0      0 127.0.0.1:3310          0.0.0.0:*               LISTEN      5783/clamd          
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      3126/rpcbind        
tcp        0      0 0.0.0.0:465             0.0.0.0:*               LISTEN      5966/master         
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      3460/sshd           
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      3477/cupsd          
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      5966/master         
tcp        0      0 127.0.0.1:7171          0.0.0.0:*               LISTEN      4098/java           
tcp        0      0 0.0.0.0:7780            0.0.0.0:*               LISTEN      5804/httpd          
tcp        0      0 192.168.124.3:389       0.0.0.0:*               LISTEN      3764/slapd          
tcp        0      0 127.0.0.1:10663         0.0.0.0:*               LISTEN      5396/zmlogger: zmrr 
tcp        0      0 127.0.0.1:10024         0.0.0.0:*               LISTEN      5546/amavisd (maste 
tcp        0      0 127.0.0.1:10025         0.0.0.0:*               LISTEN      5966/master         
tcp        0      0 0.0.0.0:5801            0.0.0.0:*               LISTEN      3608/xinetd         
tcp        0      0 127.0.0.1:7306          0.0.0.0:*               LISTEN      5383/mysqld         
tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN      5966/master         
tcp        0      0 0.0.0.0:5901            0.0.0.0:*               LISTEN      3608/xinetd         
tcp        0      0 127.0.0.1:3310          127.0.0.1:46080         TIME_WAIT   -                   
tcp        0      0 127.0.0.1:48265         127.0.0.1:10025         ESTABLISHED 5869/amavisd (ch1-a 
tcp        0      0 192.168.124.3:54273     72.14.204.118:80        ESTABLISHED 6757/firefox        
tcp        0      0 127.0.0.1:10025         127.0.0.1:48265         ESTABLISHED 17851/smtpd         
tcp        0      0 127.0.0.1:48257         127.0.0.1:10025         ESTABLISHED 5868/amavisd (ch1-a 
tcp        0      0 192.168.124.3:389       192.168.124.3:60371     ESTABLISHED 3764/slapd          
tcp        0      0 127.0.0.1:10025         127.0.0.1:48257         ESTABLISHED 17533/smtpd         
tcp        0      0 192.168.124.3:389       192.168.124.3:60361     ESTABLISHED 3764/slapd          
tcp        0      0 192.168.124.3:60674     192.168.124.3:389       ESTABLISHED 5867/amavisd (ch1-a 
tcp        0      0 192.168.124.3:389       192.168.124.3:60363     ESTABLISHED 3764/slapd          
tcp       61      0 127.0.0.1:53465         127.0.0.1:10025         CLOSE_WAIT  5867/amavisd (ch1-a 
tcp        0      0 192.168.124.3:389       192.168.124.3:60647     ESTABLISHED 3764/slapd          
tcp        0      0 192.168.124.3:52220     74.125.113.147:80       ESTABLISHED 6757/firefox        
tcp        0      0 192.168.124.3:60361     192.168.124.3:389       ESTABLISHED 17518/proxymap      
tcp        0      0 192.168.124.3:60363     192.168.124.3:389       ESTABLISHED 5868/amavisd (ch1-a 
tcp        0      0 192.168.124.3:40346     24.143.205.233:80       ESTABLISHED 6757/firefox        
tcp        0      0 192.168.124.3:60371     192.168.124.3:389       ESTABLISHED 5869/amavisd (ch1-a 
tcp        0      0 192.168.124.3:389       192.168.124.3:60674     ESTABLISHED 3764/slapd          
tcp        0      0 127.0.0.1:7171          127.0.0.1:53657         TIME_WAIT   -                   
tcp        0      0 192.168.124.3:52219     74.125.113.147:80       ESTABLISHED 6757/firefox        
tcp        0      0 192.168.124.3:60647     192.168.124.3:389       ESTABLISHED 5866/amavisd (ch2-a 
tcp        0      0 192.168.124.3:34027     72.14.204.102:80        ESTABLISHED 6757/firefox        
udp        0      0 0.0.0.0:177             0.0.0.0:*                           3553/kdm            
udp        0      0 0.0.0.0:751             0.0.0.0:*                           3126/rpcbind        
udp        0      0 0.0.0.0:111             0.0.0.0:*                           3126/rpcbind        
udp        0      0 0.0.0.0:631             0.0.0.0:*                           3477/cupsd          
udp        0      0 0.0.0.0:51090           0.0.0.0:*                           4098/java
Reply With Quote
  #6 (permalink)  
Old 12-27-2011, 05:49 AM
Zimbra Consultant & Moderator
  
Posts: 20,314
Default
Sorry, I missed the mailbox service not starting. I'd suggest you start again with the 32bit server and remove memcached then do the move to the 64bit server again.
__________________
Regards


Bill
Reply With Quote
  #7 (permalink)  
Old 12-27-2011, 05:53 AM
Advanced Member
  
Posts: 189
Default
Quote:
Originally Posted by phoenix View Post
Sorry, I missed the mailbox service not starting. I'd suggest you start again with the 32bit server and remove memcached then do the move to the 64bit server again.
What is the correct way to remove memcached from the 32 bit server? It is SLES10, can i use yast to remove memcached or is there a zimbra way to remove memcached?
Reply With Quote
  #8 (permalink)  
Old 12-27-2011, 07:26 AM
Advanced Member
  
Posts: 189
Default
OK, i followed [SOLVED] Disable/Uninstall memcached to disable/uninstall memcached on the 32 bit server and then re-started Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki. Now, when i run zmcontrol start on the 64 bit server i get:
Code:
 Starting ldap...Done.
        Starting zmconfigd...Done.
        Starting logger...Done.
        Starting mailbox...Done.
        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...Done.
        Starting spell...Done.
        Starting mta...Done.
        Starting stats...Done.
GREAT! Until i run zmcontrol status and see this:
Code:
 antispam                Running
        antivirus               Running
        ldap                    Running
        logger                  Running
        mailbox                 Stopped
                mysql.server is not running.
                zmmailboxdctl is not running.
        mta                     Running
        snmp                    Running
        spell                   Running
        stats                   Running
        zmconfigd               Running
Zmmailboxd.out shows:
Code:
0    INFO  [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
Total time for which application threads were stopped: 0.0001900 seconds
Total time for which application threads were stopped: 0.0002100 seconds
Zimbra server reserving server socket port=110 bindaddr=192.168.124.3 ssl=false
Zimbra server reserving server socket port=995 bindaddr=192.168.124.3 ssl=true
Fatal error: exception while binding to ports
java.net.SocketException: Unbound server sockets not implemented
	at javax.net.ServerSocketFactory.createServerSocket(ServerSocketFactory.java:80)
	at com.zimbra.common.util.NetUtil.newBoundServerSocket(NetUtil.java:95)
	at com.zimbra.common.util.NetUtil.bindServerSocket(NetUtil.java:163)
	at com.zimbra.common.util.NetUtil.bindSslTcpServerSocket(NetUtil.java:54)
	at com.zimbra.common.handlers.PrivilegedHandler.openPorts(PrivilegedHandler.java:82)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.mortbay.xml.XmlConfiguration.call(XmlConfiguration.java:542)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:252)
	at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
	at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.mortbay.start.Main.invokeMain(Main.java:194)
	at org.mortbay.start.Main.start(Main.java:534)
	at org.mortbay.start.Main.start(Main.java:441)
	at org.mortbay.start.Main.main(Main.java:119)
Heap
 par new generation   total 217536K, used 15499K [0x00000000bcc00000, 0x00000000cb800000, 0x00000000cb800000)
  eden space 193408K,   8% used [0x00000000bcc00000, 0x00000000bdb22da0, 0x00000000c88e0000)
  from space 24128K,   0% used [0x00000000c88e0000, 0x00000000c88e0000, 0x00000000ca070000)
  to   space 24128K,   0% used [0x00000000ca070000, 0x00000000ca070000, 0x00000000cb800000)
 concurrent mark-sweep generation total 728064K, used 0K [0x00000000cb800000, 0x00000000f7f00000, 0x00000000f8000000)
 concurrent-mark-sweep perm gen total 131072K, used 9155K [0x00000000f8000000, 0x0000000100000000, 0x0000000100000000)
Heading, "For All Versions: step "4" of Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki says: If the original server was running with commercial certificates, copy those over as well.
The origianl server was NOT running commercial certificates. Should i do this section or skip it?
Reply With Quote
  #9 (permalink)  
Old 12-27-2011, 08:06 AM
Advanced Member
  
Posts: 189
Default [SOLVED] Memcached Does Not Start
OK, i have gotten memcached working and would like to mark this thread SOLVED. I had to copy the keystore file to the 64 bit server and smtp certs.
Reply With Quote
Reply

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.