Re: [OpenIndiana-discuss] /hipster: rsyslog question
On 07/17/15 01:30 PM, Alexander Pyhalov wrote: On 07/14/2015 14:47, Predrag Zečević - Unix Systems Administrator wrote: Will wait until next reboot, for final confirmation. Hi. Did you have a chance to ensure that your manifest works on reboot? Hi Alexander, yes, just did it - works perfect... Best regards. -- Predrag Zečević Technical Support Analyst 2e Systems GmbH Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 Mobile:+49 174 3109 288, Skype: predrag.zecevic E-mail:predrag.zece...@2e-systems.com Headquarter: 2e Systems GmbH, Königsteiner Str. 87, 65812 Bad Soden am Taunus, Germany Company registration: Amtsgericht Königstein (Germany), HRB 7303 Managing director:Phil Douglas http://www.2e-systems.com/ - Making your business fly! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] /hipster: rsyslog question
On 07/14/2015 14:47, Predrag Zečević - Unix Systems Administrator wrote: Will wait until next reboot, for final confirmation. Hi. Did you have a chance to ensure that your manifest works on reboot? -- Best regards, Alexander Pyhalov, system administrator of Southern Federal University IT department ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] /hipster: rsyslog question
On 07/14/15 01:47 PM, Predrag Zečević - Unix Systems Administrator wrote:
On 07/14/15 12:30 PM, Alexander Pyhalov wrote:
On 07/14/2015 10:31, Predrag Zečević - Unix Systems Administrator wrote:
Hi all,
That dumpadm was started AFTER 1st attempt of rsyslog... Also, sym-link
confirmes that:
$ ls -alL /dev/dump
crw-rw 1 root sys 281, 0 Jul 14 08:52 /dev/dump
$ ls -al /dev/dump
lrwxrwxrwx 1 root root 29 Nov 21 2013 /dev/dump ->
../devices/pseudo/dump@0:dump
$ ls -al /devices/pseudo/dump@0:dump
crw-rw 1 root sys 281, 0 Jul 14 08:52 /devices/pseudo/dump@0:dump
So, how I can make either that dumpadm runs BEFORE rsyslog or rsyslog
AFTER dumpadm?
Any ideas?
Hi. Try to look at syslog dependencies. It seems some of them should be
added to rsyslog.
Hi Alexander,
look like that was problem (attached modified version here - changes
merged from /lib/svc/manifest/system/system-log.xml - only dependency
sections):
$ pfexec svccfg validate manifest-rsyslog.xml
[no error]
$ pfexec svccfg import manifest-rsyslog.xml
[no error]
$ pfexec svcadm refresh rsyslog
$ pfexec svcadm restart rsyslog
[no error]
$ tail -10 $(svcs -L rsyslog)
[ Jul 14 08:52:13 Executing start method ("/lib/svc/method/rsyslog"). ]
[ Jul 14 08:52:13 Method "start" exited with status 0. ]
[ Jul 14 12:57:22 Rereading configuration. ]
[ Jul 14 12:57:23 Executing refresh method (:kill). ]
[ Jul 14 12:57:33 Rereading configuration. ]
[ Jul 14 12:57:33 Executing refresh method (:kill). ]
[ Jul 14 12:57:38 Stopping because service restarting. ]
[ Jul 14 12:57:38 Executing stop method (:kill). ]
[ Jul 14 12:57:38 Executing start method ("/lib/svc/method/rsyslog"). ]
[ Jul 14 12:57:38 Method "start" exited with status 0. ]
Verifying changes:
$ pfexec svccfg export system/system-log
Will wait until next reboot, for final confirmation.
Thank you for tip.
With best regards.
Attachment was removed, so:
$ pfexec svccfg export system/system-log
'/usr/share/lib/xml/dtd/service_bundle.dtd.1'>
restart_on='none' type='service'>
restart_on='none' type='service'>
restart_on='none' type='service'>
restart_on='none' type='service'>
grouping='optional_all'>
exec='/lib/svc/method/rsyslog' timeout_seconds='600'/>
timeout_seconds='60'/>
timeout_seconds='60'/>
reliable and extended system log
daemon
--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH
Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49 174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com
Headquarter: 2e Systems GmbH, Königsteiner Str. 87,
65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas
http://www.2e-systems.com/ - Making your business fly!
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] /hipster: rsyslog question
14 июля 2015 г. 9:31:44 CEST, "Predrag Zečević - Unix Systems Administrator"
пишет:
>Hi all,
>
>I have enabled rsyslog service (instead of default system-log):
>
>$ svcs system-log
>STATE STIMEFMRI
>disabled8:48:36 svc:/system/system-log:default
>online 8:52:13 svc:/system/system-log:rsyslog
>
>and I am faced with strange error during reboot! From
>/var/svc/log/system-system-log:rsyslog.log:
>
>[ Jul 14 08:48:37 Executing start method ("/lib/svc/method/rsyslog"). ]
>savecore: open("/dev/dump"): No such file or directory
>[ Jul 14 08:48:42 Method "start" exited with status 0. ]
>[ Jul 14 08:48:43 Stopping because process dumped core. ]
>[ Jul 14 08:48:43 Executing stop method (:kill). ]
>[ Jul 14 08:48:43 Executing start method ("/lib/svc/method/rsyslog"). ]
>savecore: open("/dev/dump"): No such file or directory
>[ Jul 14 08:48:43 Method "start" exited with status 0. ]
>[ Jul 14 08:48:43 Stopping because process dumped core. ]
>[ Jul 14 08:48:43 Executing stop method (:kill). ]
>[ Jul 14 08:48:43 Executing start method ("/lib/svc/method/rsyslog"). ]
>savecore: open("/dev/dump"): No such file or directory
>[ Jul 14 08:48:43 Method "start" exited with status 0. ]
>[ Jul 14 08:48:43 Stopping because process dumped core. ]
>[ Jul 14 08:48:43 Executing stop method (:kill). ]
>[ Jul 14 08:48:43 Executing start method ("/lib/svc/method/rsyslog"). ]
>savecore: open("/dev/dump"): No such file or directory
>[ Jul 14 08:48:43 Method "start" exited with status 0. ]
>[ Jul 14 08:48:43 Stopping because process dumped core. ]
>[ Jul 14 08:48:43 Executing stop method (:kill). ]
>[ Jul 14 08:48:43 Restarting too quickly, changing state to
>maintenance. ]
>
>So, it went to maintenance, because /dev/dump link wasn't created
>BEFORE
>rsyslog is started (it is managed by svc:/system/dumpadm:default
>service, right?). From /var/svc/log/system-dumpadm:default.log we see:
>
>[ Jul 14 08:48:39 Enabled. ]
>[ Jul 14 08:49:41 Executing start method
>("/lib/svc/method/svc-dumpadm"). ]
>[ Jul 14 08:49:42 Method "start" exited with status 0. ]
>savecore: bad magic number 6db6db6d
>
>
>That dumpadm was started AFTER 1st attempt of rsyslog... Also, sym-link
>
>confirmes that:
>
>$ ls -alL /dev/dump
>crw-rw 1 root sys 281, 0 Jul 14 08:52 /dev/dump
>$ ls -al /dev/dump
>lrwxrwxrwx 1 root root 29 Nov 21 2013 /dev/dump ->
>../devices/pseudo/dump@0:dump
>$ ls -al /devices/pseudo/dump@0:dump
>crw-rw 1 root sys 281, 0 Jul 14 08:52 /devices/pseudo/dump@0:dump
>
>So, how I can make either that dumpadm runs BEFORE rsyslog or rsyslog
>AFTER dumpadm?
>
>Any ideas?
>
>With best regards.
>
>--
>Predrag Zečević
>Technical Support Analyst
>2e Systems GmbH
>
>Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
>Mobile:+49 174 3109 288, Skype: predrag.zecevic
>E-mail:predrag.zece...@2e-systems.com
>
>Headquarter: 2e Systems GmbH, Königsteiner Str. 87,
> 65812 Bad Soden am Taunus, Germany
>Company registration: Amtsgericht Königstein (Germany), HRB 7303
>Managing director:Phil Douglas
>
>http://www.2e-systems.com/ - Making your business fly!
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss
Run 'svccfg -s rsyslog editprop' and add the dependency entries similar to
those where services depend on network, or fs-local, or somesuch.
Then svcadm refresh rsyslog.
HTH, Jim
--
Typos courtesy of K-9 Mail on my Samsung Android
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] /hipster: rsyslog question
On 07/14/15 12:30 PM, Alexander Pyhalov wrote:
On 07/14/2015 10:31, Predrag Zečević - Unix Systems Administrator wrote:
Hi all,
That dumpadm was started AFTER 1st attempt of rsyslog... Also, sym-link
confirmes that:
$ ls -alL /dev/dump
crw-rw 1 root sys 281, 0 Jul 14 08:52 /dev/dump
$ ls -al /dev/dump
lrwxrwxrwx 1 root root 29 Nov 21 2013 /dev/dump ->
../devices/pseudo/dump@0:dump
$ ls -al /devices/pseudo/dump@0:dump
crw-rw 1 root sys 281, 0 Jul 14 08:52 /devices/pseudo/dump@0:dump
So, how I can make either that dumpadm runs BEFORE rsyslog or rsyslog
AFTER dumpadm?
Any ideas?
Hi. Try to look at syslog dependencies. It seems some of them should be
added to rsyslog.
Hi Alexander,
look like that was problem (attached modified version here - changes
merged from /lib/svc/manifest/system/system-log.xml - only dependency
sections):
$ pfexec svccfg validate manifest-rsyslog.xml
[no error]
$ pfexec svccfg import manifest-rsyslog.xml
[no error]
$ pfexec svcadm refresh rsyslog
$ pfexec svcadm restart rsyslog
[no error]
$ tail -10 $(svcs -L rsyslog)
[ Jul 14 08:52:13 Executing start method ("/lib/svc/method/rsyslog"). ]
[ Jul 14 08:52:13 Method "start" exited with status 0. ]
[ Jul 14 12:57:22 Rereading configuration. ]
[ Jul 14 12:57:23 Executing refresh method (:kill). ]
[ Jul 14 12:57:33 Rereading configuration. ]
[ Jul 14 12:57:33 Executing refresh method (:kill). ]
[ Jul 14 12:57:38 Stopping because service restarting. ]
[ Jul 14 12:57:38 Executing stop method (:kill). ]
[ Jul 14 12:57:38 Executing start method ("/lib/svc/method/rsyslog"). ]
[ Jul 14 12:57:38 Method "start" exited with status 0. ]
Verifying changes:
$ pfexec svccfg export system/system-log
Will wait until next reboot, for final confirmation.
Thank you for tip.
With best regards.
--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH
Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49 174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com
Headquarter: 2e Systems GmbH, Königsteiner Str. 87,
65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas
http://www.2e-systems.com/ - Making your business fly!
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] /hipster: rsyslog question
On 07/14/2015 10:31, Predrag Zečević - Unix Systems Administrator wrote: Hi all, That dumpadm was started AFTER 1st attempt of rsyslog... Also, sym-link confirmes that: $ ls -alL /dev/dump crw-rw 1 root sys 281, 0 Jul 14 08:52 /dev/dump $ ls -al /dev/dump lrwxrwxrwx 1 root root 29 Nov 21 2013 /dev/dump -> ../devices/pseudo/dump@0:dump $ ls -al /devices/pseudo/dump@0:dump crw-rw 1 root sys 281, 0 Jul 14 08:52 /devices/pseudo/dump@0:dump So, how I can make either that dumpadm runs BEFORE rsyslog or rsyslog AFTER dumpadm? Any ideas? Hi. Try to look at syslog dependencies. It seems some of them should be added to rsyslog. -- Best regards, Alexander Pyhalov, system administrator of Southern Federal University IT department ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] /hipster: rsyslog question
Hi all,
I have enabled rsyslog service (instead of default system-log):
$ svcs system-log
STATE STIMEFMRI
disabled8:48:36 svc:/system/system-log:default
online 8:52:13 svc:/system/system-log:rsyslog
and I am faced with strange error during reboot! From
/var/svc/log/system-system-log:rsyslog.log:
[ Jul 14 08:48:37 Executing start method ("/lib/svc/method/rsyslog"). ]
savecore: open("/dev/dump"): No such file or directory
[ Jul 14 08:48:42 Method "start" exited with status 0. ]
[ Jul 14 08:48:43 Stopping because process dumped core. ]
[ Jul 14 08:48:43 Executing stop method (:kill). ]
[ Jul 14 08:48:43 Executing start method ("/lib/svc/method/rsyslog"). ]
savecore: open("/dev/dump"): No such file or directory
[ Jul 14 08:48:43 Method "start" exited with status 0. ]
[ Jul 14 08:48:43 Stopping because process dumped core. ]
[ Jul 14 08:48:43 Executing stop method (:kill). ]
[ Jul 14 08:48:43 Executing start method ("/lib/svc/method/rsyslog"). ]
savecore: open("/dev/dump"): No such file or directory
[ Jul 14 08:48:43 Method "start" exited with status 0. ]
[ Jul 14 08:48:43 Stopping because process dumped core. ]
[ Jul 14 08:48:43 Executing stop method (:kill). ]
[ Jul 14 08:48:43 Executing start method ("/lib/svc/method/rsyslog"). ]
savecore: open("/dev/dump"): No such file or directory
[ Jul 14 08:48:43 Method "start" exited with status 0. ]
[ Jul 14 08:48:43 Stopping because process dumped core. ]
[ Jul 14 08:48:43 Executing stop method (:kill). ]
[ Jul 14 08:48:43 Restarting too quickly, changing state to maintenance. ]
So, it went to maintenance, because /dev/dump link wasn't created BEFORE
rsyslog is started (it is managed by svc:/system/dumpadm:default
service, right?). From /var/svc/log/system-dumpadm:default.log we see:
[ Jul 14 08:48:39 Enabled. ]
[ Jul 14 08:49:41 Executing start method ("/lib/svc/method/svc-dumpadm"). ]
[ Jul 14 08:49:42 Method "start" exited with status 0. ]
savecore: bad magic number 6db6db6d
That dumpadm was started AFTER 1st attempt of rsyslog... Also, sym-link
confirmes that:
$ ls -alL /dev/dump
crw-rw 1 root sys 281, 0 Jul 14 08:52 /dev/dump
$ ls -al /dev/dump
lrwxrwxrwx 1 root root 29 Nov 21 2013 /dev/dump ->
../devices/pseudo/dump@0:dump
$ ls -al /devices/pseudo/dump@0:dump
crw-rw 1 root sys 281, 0 Jul 14 08:52 /devices/pseudo/dump@0:dump
So, how I can make either that dumpadm runs BEFORE rsyslog or rsyslog
AFTER dumpadm?
Any ideas?
With best regards.
--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH
Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49 174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com
Headquarter: 2e Systems GmbH, Königsteiner Str. 87,
65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas
http://www.2e-systems.com/ - Making your business fly!
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
