Symantec Access Management

I am getting below error while stopping the web server.

httpd: Syntax error on line 66 of /software/bea/apache_dev_Portal_d2_Int/2.4.23/conf/httpd.conf: Cannot load /software/bea/devportal_internal_CA/webagent/bin/libmod_sm24.so into server: libsmerrlog.so: cannot open shared object file: No such file or directory

I have checked the below things.

Environment variables set for the correct path.

SELinux is permissive

web server user and web agent user are same with no permission issues.

One thing I noticed here is if I do a locate to the file libsmerrlog.so, it will not list. But when I go to the bin folder I am seeing the file with proper permission.

I am using apache 2.4.3 with web agent 12.51 SP1 CR06

Basavaraj.amasi

It seems like the environment variables are not being up by Web Server.

I see that you've mentioned "Environment variables set for the correct path"; the question is have you sourced the environmental variable file by either manually sourcing it OR defining it under 'setenv.sh' from where Apache would load it.

Try this.....

1. Source ENV file manually by running 'source ca_wa_env.sh' at Web Agent install home directory.

2. Stop Apache.

Alternative

1. Stop Apache.

2. source the ca_wa_env.sh file within setenv.sh file within Apache Home Directory.

3. Start Apache.

4. Stop Apache.

I believe Hubert is on the right track about the environment variables. It might help to know where/how the env vars are sourced.

It might also help if you can clarify how the Agent was successfully started.

Is it setup to run as a service? Or was it manually started as well?

The reason I ask is that the startup script might have the env vars sourced, but not the specific user that issued the stop. Similarly if Apache was started by UserA who has the env vars in their profile but UserB stopping Apache does not.

As for the locate not working, you may want to check with the System Admin if they have mlocate in the cron or some other script that runs updatedb. If it never runs, locate can't find new files added to the system. Find should still work as I don't believe it relies on the database that locate does.

Thanks David and Hubert, It was a minor error in apache.conf which lead to this. Now it is working fine.