'Server listener failed to start' or 'Address already in use' Error

"...Listen fail" or "Server listener failed to start, retrying: Address already in use" error on one or more GWAVA modules

When GWAVA's modules start they bind to a port number.  GWAVA QMS binds to port 49285.  If it can't bind to that port, then you will see a 'failed to bind to listener address' error or something similar.

Usually this error is caused by duplicate modules being simultaneously loaded, causing port conflicts.  Follow these steps to assure that only one of each GWAVA module is running:

For NetWare:

1)  Shut down GWAVA (gwavadn). 

If GWAVA won't unload cleanly, you may need to spawn an emergency console and run 'killgwava', then 'gwavadn' again.

2)  After GWAVA is shut down, run a module check from the System Console to make sure there aren't any hidden modules: 

m gwa* 

This will list all running nlms that begin with gwa.  Aside from gwavavsa.nlm or gwavaosa.nlm, everything else should be unloaded.  If not, then manually unload any other GWAVA modules by typing 'unload gwavamodule.nlm'.  Here is a list of the GWAVA modules and the ports that they bind to:

https://support.microfocus.com/kb/doc.php?id=7019667

If one or more GWAVA modules isn't able to be unloaded, then a server restart may be necessary.

3)  Restart GWAVA (gwavaup) 

If error remains, please call Technical Support

For Linux:

1)  Shut down GWAVA (rcgwavaman stop from a terminal).  Run a status check to make sure everything unloaded (rcgwavaman status).  If one or more GWAVA process won't unload, you may need to restart the server.

2)  After GWAVA is shut down, run a process check from a terminal to make sure there aren't any hidden processes: 

ps aux | grep gwa*

This will list all running processes that begin with gwa.  Everything should now be unloaded.  Here is a list of the GWAVA modules and the ports they bind to:

https://support.microfocus.com/kb/doc.php?id=7019667

If one or more GWAVA modules isn't able to be unloaded, then a server restart may be necessary.

3)  Restart 2 GWAVA processes. 

1. rcgwavaman start gwava
2. rcgwavaman start gwavaman

4) Now start gwavaman (rcgwavaman start)

If error remains, please call Technical Support

This article was originally published in the GWAVA knowledgebase as article ID 288.