aware_support3
Start by reading the error. Most start-up problems tell you the cause in the first red lines.
šĀ Where to look
| What you run | Where the error is |
|---|
| Control Panel | ClickĀ View outputĀ for the AwareIM Server and for Tomcat |
| Any start method | AwareIM/STARTUP_LOGS |
| Windows service | AwareIM/bin/wrapper.log |
Then find your message below.
šŖĀ 1. āPort ā¦ already in useā, āanother instance is runningā, āAddress already in useā
This is a port or a stuck Java process. Follow the steps inĀ Unable to open TCP/IP socket on port 9005. The same steps work for ports 9000, 8005, 8080 and 61616.
šļøĀ 2. āCannot create or locate the databasesā, āAccess deniedā, āSUPER privilegeā
AwareIM cannot reach its database.
ā
Fix:
Make sure MySQL, MariaDB or SQL Server is running.
Check the database name, user and password inĀ AwareIM/bin/BASServer.props.
MySQL: the account must be allowed to connect fromĀ localhost. It also needs admin rights. Without them you getĀ max_allowed_packet ā¦ need SUPER privilege.
Check free disk space. A full disk stops the database from starting.
If the database is corrupt, restore it from your backup.
š§ Ā 3. Memory errors
| Message | Cause | Fix |
|---|
Could not reserve enough space for object heap | AwareIM asks for more memory than the machine has free | Lower the memory setting, or free RAM on the server |
java.lang.OutOfMemoryError: Java heap space | AwareIM ran out of memory | Raise the memory setting |
ā
Where to set memory:
Control Panel āĀ Settings. This writes toĀ AwareIM/bin/startupOptions.props.
If you run as a Windows service, changeĀ wrapper.java.maxmemoryĀ in bothĀ AwareIM/bin/wrapper.confĀ andĀ AwareIM/bin/awareim.conf.
āĀ 4. āCould not create the Java Virtual Machineā (often after an upgrade)
An old start-up file has Java options that the new Java does not accept.
ā
Fix:
RenameĀ AwareIM/bin/startupOptions.propsĀ toĀ startupOptions.props.old.
Start AwareIM again.
Set your memory again in Control Panel āĀ Settings. The memory settings were in the file you renamed.
On Linux, AwareIM needs JDK 17 or later. A JRE is not enough.
šØĀ 5. āUnable to start the JMS queuesā, āUnknownHostExceptionā
The server cannot find itself on the network.
ā
Fix:
Make sureĀ localhostĀ points toĀ 127.0.0.1Ā in your hosts file. On Windows the file isĀ C:\Windows\System32\drivers\etc\hosts.
If you put a custom server name inĀ BASServer.props, check it is still there. The Control PanelĀ SettingsĀ dialogs can rewrite this file back toĀ localhost.
šĀ 6. Broken files after an install or upgrade
šĀ 7. āLicense expired or invalidā
This usually happens after you move to new hardware or a new VM, because the machine ID changed. Email Support with your license details.
šŖĀ 8. Runs from the Control Panel but not as a service (or the reverse)
Install and start the service as Administrator.
ReadĀ AwareIM/bin/wrapper.log.
Make sure the memory settings inĀ wrapper.confĀ match the ones you use in the Control Panel.
ā¹ļøĀ Safe to ignore
These messages do not stop the server:
Still stuck? Post the first error lines from the output orĀ STARTUP_LOGS, plus your AwareIM version and build.
