The package gpg-pubkey-b481ca4d listed in the installation-guide is not part of the SLES9. I think the package that is ment is the "suse-build-key".
But my problem now is that I have a nav3rc1 running on SLES, and everything "seems" to be running except web-interface and Alertengine.
I have used the SuSE rpm package. And is trying to find whats wrong with the apache-config. I have tried to look at the http://svn.nav.ntnu.no/nav/navme/trunk/doc/apache/httpd2.conf.example
But the apache-structer is totaly different from my debian-nav3-beta10 installation. Anyone have a suggestion where to start?
/usr/local/nav/bin/nav status networkDiscovery: Up cricket: Up eventEngine (pid 6435) is running... iptrace: Up backup: Up servicemon.py (pid 6467) is running... smsd.pl (pid 6491) is running... thresholdMon: Up mactrace: Up logengine: Up safe_smsd: Up Alertengine is not running.
maintengine: Up pping.py (pid 6520) is running... getDeviceData (pid 6546) is running...
Peder Sefland
Morten Vold morten.vold@ntnu.no 23.06.05 13:04 >>>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 23/06/2005 11:42, Peder Magne Sefland uttered:
But a search on google show me that SuSE Linux Professional 9.3 has this package. Has this document been writen based on Professional 9.3 or SLES9 ?
The document was originally written for SLES9, but I see Tristan Rhodes has edited the page since then - specifically he altered the part about manually installing Perl-DBD-Pg into installing it from Yast [1]
I haven't confirmed that his changes were valid, but if the perl-DBD-Pg package really isn't part of standard SLES9, then that part of his page change should be reverted.
Can I use the Professional 9.3 perl-DBD-Pg-rpm on my SLES9?
Don't know, you'll have to try it and see for yourself.
[1] http://metanav.ntnu.no/moin.cgi/InstallingOnSLES?action=diff&date2=11120...
- -- Morten Vold NTNU ITEA Integrasjonsgruppen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 27/06/2005 23:52, Peder Magne Sefland uttered:
The package gpg-pubkey-b481ca4d listed in the installation-guide is not part of the SLES9. I think the package that is ment is the "suse-build-key".
The package list in the installation guide is derived from a diff between the output of "rpm -qa" before and after the installation of NAV. This means that some of the packages on the list may have been automatically installed by Yast as dependencies of other packages that were marked for installation manually.
http://svn.nav.ntnu.no/nav/navme/trunk/doc/apache/httpd2.conf.example
But the apache-structer is totaly different from my debian-nav3-beta10 installation. Anyone have a suggestion where to start?
Well, looking back at our local configuration, most of the changes made to the default config in SLES9 seems to have been made in two files:
default-server.conf and vhosts.d/ssl-vhost.conf (the latter may just be a modified version of vhosts.d/vhost-ssl.template).
I will send you a copy of these configuration files (off-list).
- -- Morten Vold NTNU ITEA Integrasjonsgruppen
From arajgarh at iwu.edu Wed Jun 29 14:56:58 2005
From: arajgarh at iwu.edu (Aditya Rajgarhia) Date: Wed Jun 29 20:57:12 2005 Subject: [Nav-users] Installation Trouble Message-ID: 6542194.1120071418077.JavaMail.arajgarh@iwu.edu
I'm trying to install NAV on Gentoo Linux and have problems.
If I use the rpm, it complains that I don't ahve python, perl, bind-utils, postgresql isntalled even though I DO have newer versions of all.
If I try to compile from source, it complains a lot when it gets to the SimpleSnmp package: Cannot resolve symbol
Can someone help? I've been trying to install this for a week, my boss needs it fast :(
Thanks,
Aditya
---------------- Aditya Rajgarhia 305 Kemp Hall x2042 arajgarh@iwu.edu
From kreide at gmail.com Wed Jun 29 13:09:11 2005
From: kreide at gmail.com (Kristian Eide) Date: Wed Jun 29 21:09:17 2005 Subject: [Nav-users] Installation Trouble In-Reply-To: 6542194.1120071418077.JavaMail.arajgarh@iwu.edu References: 6542194.1120071418077.JavaMail.arajgarh@iwu.edu Message-ID: b4c110fd050629120942fc69ff@mail.gmail.com
If I try to compile from source, it complains a lot when it gets to the SimpleSnmp package: Cannot resolve symbol
You need the Java SNMP package:
http://edge.mcs.drexel.edu/GICL/people/sevy/snmp/
Build it and put the resulting JAR in your jre/lib/ext directory.