Closed davison closed 8 years ago
It seems am_web_init() is failing. You need to check logs/amAgent Thank you.
yes, as I mentioned, that log file never gets created. Its location is defined correctly in the config file, and the permissions on the file system are correct, but the file is not created so I can't trouble shoot this any further. I think the plugin fails before it even gets that far.
hmm.. if I run the nginx as root it works :) Not sure why this is needed, it's binding a high port to listen on and is running in a working directory where all the dir/file permissions look correct for unpriviliged use. Even running the server under strace didn't provide any indication as to what the requirement for a root user was.
i don't understand your permission issue... It might to related to ACL permission? Any way, you can out put debug log by edit conf/OpenSSOAgentBootstrap.properties com.sun.identity.agents.config.debug.level = /tmp/amAgent
I tried the pre-built CentOS6 binary, and also tried building from source. Both gave exactly the same results which is that the plugin fails to load correctly (I assume). It never contacts the naming service on the target OpenAM server - checked with tcpdump - and despite a high log level being set, it never even gets as far as creating the logfile so it seems to fail at a VERY early stage in the plugin operation.
Output from the server (with
daemon off;
) looks like this:In the above output, the line break has been added after server startup, the following output is the result of a single request being made to the server.