Forum OpenACS Q&A: where can i change the default url for oacs-9.5?
i have gone through the administration and expected to find something in the parameter settings but didn't. Hopefully, there's a file I can edit.
You're probably looking for the value for parameter SystemURL in acs-kernel http://openacs.org/api-doc/proc-view?proc=ad_url
I'll dig around abit locally via psql, but you might find it before I do, since you're already apparently looking at parameters.
psql to the db. Something like:
su - postgres psql oacs-5-9
Then you can get the parameter_id:
oacs-5-9=# select * from apm_parameter_values where parameter_id in (select parameter_id from apm_parameters where parameter_name = 'SystemURL');
value_id | package_id | parameter_id | attr_value ----------+------------+--------------+------------------------------------ 74 | 69 | 64 | http://localhost:8000 (1 row)
ultimately we need the dotlrn working
Basically, the url is determined by SystemURL and the info provided in the nsd config.tcl file.
SystemURL needs the "http://" prefix as shown above. The domain in config.tcl doesn't.
ps. As a noobie over the years, I've broken the system a few times by changing that value, where once it was changed I couldn't login to admin to change it back via a browser. I had to access the db via psql. If this is the problem, you can always change it back via the db.
Concerning running as a service: Depending on the version of linux, install-ns creates either a UpStart file (usage: status|start|stop oacs-5.9) and/or a systemd file (usage: systemctl status|start|stop oacs-5.9). running on older Ubuntus, you get upstart, some ubuntu versions support upstart and systemd (where the script generates both), redhat/fedora/centus use sytemd. When you change e.g. IP-addresses and/or ports, you have to update the service files in use as well (see the comments in the service files).
thanks for the nsd autostart solution with systemctl.
now onto other fish to fry under another post.
dotlrn and email for notification the final 2 for an out of the box install, for me.
I ran the StartUp command, and it was not there when i went to install it. what should i do.
/lib/systemd/system/, other configuration might expect it under
/etc/systemd/system/. Remember, after you have installed the .service file, you have do a
systemctl daemon-reloadand you have to do a
systemctl enable ...to make it active for restarts of the operating system (check with
systemctl is-enabled ...). You can list all services known to systemd with
hope this helps.
Reason why it was not working is that probably Debian is a special case with respect to Ubuntu, as it doesn't ship upstart out of the box. Dind't take time to think about a proper fix, but it should just be some "if" revision.
Anyway, for what concerns Kenneth, give a look toward the end of the script and you'll see that systemd service creation is decided upon the value of a couple of flags. Check if your installation passes through the service creation part and if doesn't you can try hardcoding the flags.
The problem is/was that some recent versions of Ubuntu start to support systemd. Since 07/02/2016, the install script checks, whether it is running on a systemd-capable version of Ubuntu and generates in this case an upstart and a systemd .service file (see also )
My impression was that Kenneth was using a fresh version of install-ns, probably on a "recent" version of Ubuntu.
PS: For problem reports concerning system integration, please always write the exact version of the Operating System, since this helps reducing the guess work, since everything is in flux.
your instructions were exactly what I needed.
kmw@fremont:/lib/systemd/system$ sudo nano oacs-5-9.service
kmw@fremont:/lib/systemd/system$ sudo systemctl daemon-reload
kmw@fremont:/lib/systemd/system$ sudo systemctl enable oacs-5-9.service
kmw@fremont:/lib/systemd/system$ sudo systemctl is-enable oacs-5-9.service
Unknown operation is-enable.
kmw@fremont:/lib/systemd/system$ sudo systemctl is-enabled oacs-5-9.service
thank you very very much.