Hi! lmsig_gt.so does not exit anywhere in my system. same issue i am facing in ubuntu as well.
On Tue, Mar 4, 2014 at 10:12 AM, Muhammad Asif <[email protected]> wrote: > Hi! > > Thanks for your prompt reply. > I have already search this file "lmsig_gt.so" in my system but it is no > where. > > > > On Mon, Mar 3, 2014 at 11:11 PM, David Lang <[email protected]> wrote: > >> On Mon, 3 Mar 2014, Muhammad Asif wrote: >> >> Hi! Rsyslog Family >>> >>> It has become our utmost desire to install rsyslog v7.5 or rsyslog v8 >>> with >>> Guardtime enabled to sign signatures on Debian6 (I can't change it due to >>> certain reason). Today after a great effort we successfully install >>> rsyslog >>> v8 in Debian6 showing libgt0 installed. Add in rsyslog.conf. >>> >>> action(type="omfile" file="/var/log/logfile" >>> >>> sig.provider="gt" >>> >>> sig.keepTreeHashes="on" >>> >>> sig.keepRecordHashes="on") >>> >>> >>> But issue is .gtsig file is not create and when I run rsyslogd -N1, I >>> receive the following error with some deprications. >>> >>> >>> rsyslogd: warning: ~ action is deprecated, consider using the 'stop' >>> statement instead [try http://www.rsyslog.com/e/2307 ] >>> >> >> this you can ignore. >> >> rsyslogd: could not load module '*/usr/lib/rsyslog/lmsig_gt.so'*, >>> dlopen: >>> >>> /usr/lib/rsyslog/lmsig_gt.so: cannot open shared object file: No such >>> file >>> or directory [try http://www.rsyslog.com/e/2066 ] >>> >> >> I think this is the key problem. does this file exist elsewhere in your >> system? >> >> It looks as if the gt related stuff is in a separate package from the >> base rsyslog packages. I see the libgt and libgt0 packages in the debian >> package repository at the adiscon site. They sound like what you are >> needing. >> >> rsyslogd: omfile: could not load signature provider *'lmsig_gt' - >>> signatures disabled* [try http://www.rsyslog.com/e/1006 ] >>> >> >> again indication of the gt support not being installed. >> >> rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line >>> 132: parameter *'sig.keepRecordHashes*' not known -- typo in config file? >>> >>> [try http://www.rsyslog.com/e/2207 ] >>> >>> rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line >>> 132: parameter *'sig.keepTreeHashes'* not known -- typo in config file? >>> [try http://www.rsyslog.com/e/2207 ] >>> >> >> These errors are caused by the modules not being loaded. The syntax of >> the config files is not fixed, it's defined piecemeal in each module that >> you load, so if you fail to load a module, any config statements related to >> that module will now generate this sort of error. >> >> David Lang >> _______________________________________________ >> rsyslog mailing list >> http://lists.adiscon.net/mailman/listinfo/rsyslog >> http://www.rsyslog.com/professional-services/ >> What's up with rsyslog? Follow https://twitter.com/rgerhards >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad >> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you >> DON'T LIKE THAT. >> > > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
