Forum OpenACS Q&A: Unable to access ad.ini in ../../parameters

1: Unable to access ad.ini in ../../parameters

Posted by Ken Chakiris on 04/04/00 01:32 AM

I was only able to get ACS/pg working properly by combining the
nsd.ini and the ad.ini file using cat and creating one big
nsd.ini.test file. For some reason, the server wasn't reading the
ad.in file in the ../../parameters directory. What did I do wrong? I
followed the instructions in the installation guide for beginners.
(This link now seems be broken on this site for some reason).

The systems seems to be working now and I am going throught the
recommended series of tests.

2: Response to Unable to access ad.ini in ../../parameters (response to 1)

Posted by Phillip Harrington on 04/04/00 03:18 AM

Rename ad.ini to be yourservicename.ini. So in my case my server is "server1" so I did:

mv ad.ini server1.ini

Also edit it so all the [ns/server/yourserver/ad] sections have your service name instead of "yourserver" or whatever the default value is. So for me these all read:

[ns/server/server1/ad/comments] or whatever

Then make sure your nsd.ini found in /home/nsadmi (or your NS_HOME) has auxconfigdir=/web/server1/www/parameters (where server1 is your server name) listed under [ns/parameters]

Good luck. Check the arsdigita pages for help too.

3: Response to Unable to access ad.ini in ../../parameters (response to 1)

Posted by Ben Adida on 04/04/00 03:38 AM

a quick clarification because it sometimes can lead to errors. Any files that are named .ini in the auxconfigdir are read, so you don't need to name your .ini file anything specific.

4: Response to Unable to access ad.ini in ../../parameters (response to 1)

Posted by Phillip Harrington on 04/04/00 03:56 AM

Really? I thought the name had to match the service name? In my case as long as it was ad.ini it was not being read at all. Maybe that was not the cause though. Hmmm...

Phil