-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDQ7BKXxIl0kpcOkQRAmBXAKC1PqQBRaccCZrR2WjZfeh/yPxKJQCgyZfC O3qoTQD4aPx+fQchoW0XAF0= =dFkM -----END PGP SIGNATURE----- >From morten.vold at ntnu.no Wed Oct 5 13:53:46 2005 From: morten.vold at ntnu.no (Morten Vold) Date: Wed Oct 5 12:54:11 2005 Subject: [Nav-users] Upgrade guide? In-Reply-To: 20050919173552.D13EF33724@signal.itea.ntnu.no References: 20050919173552.D13EF33724@signal.itea.ntnu.no Message-ID: 4343B0BA.5010308@ntnu.no -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/09/2005 19:35, Joshua Sidwell uttered: > Is there any documentation for upgrading from the beta to the 3.0 gold? Not really, it basically goes like this: 1. Stop NAV. 2. Install new version. 4. Make sure the alertengine.cfg file is updated with the new errorlog parameter (see the example config file in the distribution, unless you use a packaging system that installs it for you - like apt og rpm). 3. Start NAV. - -- Morten Vold NTNU ITEA Integrasjonsgruppen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDQ7C6XxIl0kpcOkQRArW5AKDQ6MmdXd+wcvao33j+QgxPIpyvjQCcC0WF jKn23Ob77O1JMT3JluP/PbM= =++q5 -----END PGP SIGNATURE----- >From morten.vold at ntnu.no Wed Oct 5 13:59:35 2005 From: morten.vold at ntnu.no (Morten Vold) Date: Wed Oct 5 12:59:47 2005 Subject: [Nav-users] Alertengine email sender machine name != real machine name In-Reply-To: 433BB1F5.80705@hsh.no References: 433BB1F5.80705@hsh.no Message-ID: 4343B217.4000805@ntnu.no -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/09/2005 11:20, Roger Aas uttered: > As you can see it is only the "From:" header line that says > "nav.hsh.no", the rest of the headers give the correct name for the > server "nav3.hsh.no". Anyone know where this is happening? Some > config I have missed? Or a small bug lurking somewhere? Or is it just I believe some config you have missed (or that we have conveniently obscured ;) ). Check out etc/alertengine.cfg - It has the parameter "email_from", which should be set to whater you want the From:-field to contain. - -- Morten Vold NTNU ITEA Integrasjonsgruppen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDQ7IXXxIl0kpcOkQRAh1eAKCn7JrDHDCdd3V8nRxEUxcfOI4CgwCfWZz0 AzVcM7YeidCb72ppQCpuiVA= =oY0A -----END PGP SIGNATURE----- >From morten.vold at ntnu.no Wed Oct 5 14:14:36 2005 From: morten.vold at ntnu.no (Morten Vold) Date: Wed Oct 5 13:14:50 2005 Subject: [Nav-users] Urgent: SMS sending problem In-Reply-To: 4343845E.2070807@hsh.no References: 434108B4.4050702@hsh.no 4343845E.2070807@hsh.no Message-ID: 4343B59C.8070803@ntnu.no -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/10/2005 09:44, Roger Aas uttered: > I have found out what was wrong with this. The navcron user did not > have permissions on /dev/ttyS0. The fix is this command: > > usermod -G uucp navcron Good observation. Which we forgot to document :) Just added it to http://metanav.ntnu.no/moin.cgi/InstallingOnSLES If it comes up again, it should probably be part of the FAQ. > I _still_ get the email with the error message when I start NAV, but > as long as the program works I can live with that :-) Not exactly sure why. This should only happen when the database server is taken down, but it seems to happen upon restarting NAV as well. This error usually means that the SMS Daemon exits, and then is restarted by the safe_smsd cron service. - -- Morten Vold NTNU ITEA Integrasjonsgruppen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDQ7WcXxIl0kpcOkQRAsfOAJ9g02RpaTt3keVhRfH39XLI6NBdZQCePRCt Sf6p5Y5m/e1F6nx99GRgyss= =J6yw -----END PGP SIGNATURE-----