Issue:
FME Server is licensed, but under Engine management, no engines are available.
Refering to this article: Known Issue: FME Server Engines Missing Failed to Connect to Job Queue (safe.com) I've tried to delete the log from queue folder, FME can regenerate the log, but still didn't solve the issue.
Queue log information:
[6732] 25 Nov 12:14:18.692 # Creating Server TCP listening socket 127.0.0.1:6379: bind: No error
FMEserver log:
Thu-25-Nov-2021 01:53:57.238 PM INFORM fmeenginemgrnodeclient 402911 : Connecting to Job Queue localhost node host localhost port 6379.
Thu-25-Nov-2021 01:53:57.304 PM INFORM fmeenginemgrnodeclient 402911 : Connecting to Job Queue localhost node host localhost port 6379.
Thu-25-Nov-2021 01:53:57.387 PM ERROR fmeenginemgrnodeclient 402902 : Failed to connect to Job Queue. Please ensure Job Queue is started.
Thu-25-Nov-2021 01:53:57.388 PM ERROR fmeenginemgrnodeclient Could not get a resource from the pool
redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool
at redis.clients.util.Pool.getResource(Pool.java:53)
at redis.clients.jedis.JedisPool.getResource(JedisPool.java:226)
at COM.safe.fmeserver.JobRouterConfig.loadAllTags(JobRouterConfig.java:163)
at COM.safe.fmeserver.JobRouterConfig.refresh(JobRouterConfig.java:194)
at COM.safe.fmeserver.JobRouterConfig.init(JobRouterConfig.java:142)
at COM.safe.fmeserver.FMEServerJobRouter.getJobRouterConfig(FMEServerJobRouter.java:296)
at COM.safe.fmeserver.FMEServerJobRouter.checkActiveQueueNodeAlive(FMEServerJobRouter.java:144)
at COM.safe.fmeserver.jobs.EngineManagerNodeOps.checkActiveQueueNodeAlive(EngineManagerNodeOps.java:112)
at COM.safe.fmeserver.jobs.EngineManagerNodeClient.executeLeaderOp(EngineManagerNodeClient.java:90)
at COM.safe.fmeserver.database.NodeClient.run(NodeClient.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: redis.clients.jedis.exceptions.JedisDataException: ERR invalid password
at redis.clients.jedis.Protocol.processError(Protocol.java:127)
at redis.clients.jedis.Protocol.process(Protocol.java:161)
at redis.clients.jedis.Protocol.read(Protocol.java:215)
at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
at redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:239)
at redis.clients.jedis.BinaryJedis.auth(BinaryJedis.java:2139)
at redis.clients.jedis.JedisFactory.makeObject(JedisFactory.java:108)
at org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:889)
at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:424)
at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:349)
at redis.clients.util.Pool.getResource(Pool.java:49)
... 10 more
I did notice there's another application running on the same server that also got redis-server running. Not sure if this will cause the error.