OpenSolaris
Discussions Communities Projects Download Source Browser

Home » OpenSolaris Forums » smf » discuss

Thread: svc.configd running 9% CPU constant after LU b120->b121 Nevada

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 9 - Last Post: Sep 8, 2009 1:46 AM by: gheet
aorchid

Posts: 109
From: US

Registered: 9/22/06
svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Aug 25, 2009 2:23 PM
To: Communities » smf » discuss
  Click to reply to this thread Reply

I am having two issues with Nevada b121 and SMF after a Live Upgrade from b120 and I am unsure if they are related.

First, svc.configd is running constantly at 8-9% of my CPU (Ultra 20). I have never seen this happen so consistently on prior builds. It is a bit of an issue because this is an underpowered workstation for my needs, I transiently work at 80-90% CPU, so I need all of it.

Second, I disabled ipfilter and cannot get it to restart. (I first posted this on security, but noticing the svc.configd activity am posting it here). No amount of 'clear' will help and the log file is not helpful to me.

Thank you for any suggestions.

% pfexec svcs -l ipfilter
fmri svc:/network/ipfilter:default
name IP Filter
enabled true
state maintenance
next_state none
state_time Tue Aug 25 14:09:33 2009
logfile /var/svc/log/network-ipfilter:default.log
restarter svc:/system/svc/restarter:default
contract_id
dependency require_all/none svc:/system/filesystem/minimal (online)
dependency require_all/restart svc:/network/physical (multiple)
dependency require_all/restart svc:/system/identity:node (online)
dependency require_all/restart svc:/system/identity:domain (online)

Log file:

[ Aug 24 11:51:23 Enabled. ]
[ Aug 24 11:51:55 Executing start method ("/lib/svc/method/ipfilter start"). ]
Set 0 now inactive
filter sync'd
0 entries flushed from NAT table
4 entries flushed from NAT list
[ Aug 24 11:52:04 Method "start" exited with status 0. ]
[ Aug 25 13:14:16 Stopping because service disabled. ]
[ Aug 25 13:14:17 Executing stop method ("/lib/svc/method/ipfilter stop"). ]
[ Aug 25 13:14:18 Method "stop" exited with status 0. ]
[ Aug 25 13:16:43 Enabled. ]
[ Aug 25 13:16:43 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:17:13 Method or service exit timed out. Killing contract 305. ]
[ Aug 25 13:17:13 Method "start" failed due to signal KILL. ]
[ Aug 25 13:17:13 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:17:44 Method or service exit timed out. Killing contract 306. ]
[ Aug 25 13:17:44 Method "start" failed due to signal KILL. ]
[ Aug 25 13:17:44 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:18:14 Method or service exit timed out. Killing contract 307. ]
[ Aug 25 13:18:14 Method "start" failed due to signal KILL. ]
[ Aug 25 13:18:55 Leaving maintenance because disable requested. ]
[ Aug 25 13:18:55 Disabled. ]
[ Aug 25 13:23:18 Enabled. ]
[ Aug 25 13:23:18 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:23:48 Method or service exit timed out. Killing contract 309. ]
[ Aug 25 13:23:49 Method "start" failed due to signal KILL. ]
[ Aug 25 13:25:01 Leaving maintenance because clear requested. ]
[ Aug 25 13:25:01 Enabled. ]
[ Aug 25 13:25:01 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:25:31 Method or service exit timed out. Killing contract 310. ]
[ Aug 25 13:25:31 Method "start" failed due to signal KILL. ]
[ Aug 25 13:26:34 Leaving maintenance because clear requested. ]
[ Aug 25 13:26:34 Enabled. ]
[ Aug 25 13:26:34 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:27:04 Method or service exit timed out. Killing contract 311. ]
[ Aug 25 13:27:04 Method "start" failed due to signal KILL. ]
[ Aug 25 13:31:10 Leaving maintenance because clear requested. ]
[ Aug 25 13:31:10 Enabled. ]
[ Aug 25 13:31:10 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:31:40 Method or service exit timed out. Killing contract 313. ]
[ Aug 25 13:31:40 Method "start" failed due to signal KILL. ]
[ Aug 25 13:32:39 Leaving maintenance because clear requested. ]
[ Aug 25 13:32:39 Enabled. ]
[ Aug 25 13:32:39 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:33:09 Method or service exit timed out. Killing contract 314. ]
[ Aug 25 13:33:09 Method "start" failed due to signal KILL. ]
[ Aug 25 13:40:26 Leaving maintenance because disable requested. ]
[ Aug 25 13:40:26 Disabled. ]
[ Aug 25 13:49:02 Enabled. ]
[ Aug 25 13:49:02 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:49:32 Method or service exit timed out. Killing contract 316. ]
[ Aug 25 13:49:32 Method "start" failed due to signal KILL. ]
[ Aug 25 13:52:51 Leaving maintenance because clear requested. ]
[ Aug 25 13:52:51 Enabled. ]
[ Aug 25 13:52:51 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:53:21 Method or service exit timed out. Killing contract 318. ]
[ Aug 25 13:53:21 Method "start" failed due to signal KILL. ]
[ Aug 25 13:58:17 Leaving maintenance because clear requested. ]
[ Aug 25 13:58:18 Enabled. ]
[ Aug 25 13:58:18 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 13:58:48 Method or service exit timed out. Killing contract 319. ]
[ Aug 25 13:58:48 Method "start" failed due to signal KILL. ]
[ Aug 25 14:00:14 Leaving maintenance because clear requested. ]
[ Aug 25 14:00:14 Enabled. ]
[ Aug 25 14:00:14 Executing start method ("/lib/svc/method/ipfilter start"). ]
[ Aug 25 14:00:45 Method or service exit timed out. Killing contract 322. ]
[ Aug 25 14:00:45 Method "start" failed due to signal KILL. ]

Tom Whitten
thomas.whitten@sun.com
Re: [smf-discuss] svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Aug 25, 2009 3:01 PM   in response to: aorchid

  Click to reply to this thread Reply

I saw the busy configd problem, but there were also a lot of busy gnome
processes, which I attribute do
http://defect.opensolaris.org/bz/show_bug.cgi?id=10002. Once I got gnome
to quiet down by turning off nautilus and rebooting, everything worked fine.

tom

aric writes:
> I am having two issues with Nevada b121 and SMF after a Live Upgrade from b120 and I am unsure if they are related.
>
> First, svc.configd is running constantly at 8-9% of my CPU (Ultra 20). I have never seen this happen so consistently on prior builds. It is a bit of an issue because this is an underpowered workstation for my needs, I transiently work at 80-90% CPU, so I need all of it.
>
> Second, I disabled ipfilter and cannot get it to restart. (I first posted this on security, but noticing the svc.configd activity am posting it here). No amount of 'clear' will help and the log file is not helpful to me.
>
> Thank you for any suggestions.
>
> % pfexec svcs -l ipfilter
> fmri svc:/network/ipfilter:default
> name IP Filter
> enabled true
> state maintenance
> next_state none
> state_time Tue Aug 25 14:09:33 2009
> logfile /var/svc/log/network-ipfilter:default.log
> restarter svc:/system/svc/restarter:default
> contract_id
> dependency require_all/none svc:/system/filesystem/minimal (online)
> dependency require_all/restart svc:/network/physical (multiple)
> dependency require_all/restart svc:/system/identity:node (online)
> dependency require_all/restart svc:/system/identity:domain (online)
>
> Log file:
>
> [ Aug 24 11:51:23 Enabled. ]
> [ Aug 24 11:51:55 Executing start method ("/lib/svc/method/ipfilter start"). ]
> Set 0 now inactive
> filter sync'd
> 0 entries flushed from NAT table
> 4 entries flushed from NAT list
> [ Aug 24 11:52:04 Method "start" exited with status 0. ]
> [ Aug 25 13:14:16 Stopping because service disabled. ]
> [ Aug 25 13:14:17 Executing stop method ("/lib/svc/method/ipfilter stop"). ]
> [ Aug 25 13:14:18 Method "stop" exited with status 0. ]
> [ Aug 25 13:16:43 Enabled. ]
> [ Aug 25 13:16:43 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:17:13 Method or service exit timed out. Killing contract 305. ]
> [ Aug 25 13:17:13 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:17:13 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:17:44 Method or service exit timed out. Killing contract 306. ]
> [ Aug 25 13:17:44 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:17:44 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:18:14 Method or service exit timed out. Killing contract 307. ]
> [ Aug 25 13:18:14 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:18:55 Leaving maintenance because disable requested. ]
> [ Aug 25 13:18:55 Disabled. ]
> [ Aug 25 13:23:18 Enabled. ]
> [ Aug 25 13:23:18 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:23:48 Method or service exit timed out. Killing contract 309. ]
> [ Aug 25 13:23:49 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:25:01 Leaving maintenance because clear requested. ]
> [ Aug 25 13:25:01 Enabled. ]
> [ Aug 25 13:25:01 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:25:31 Method or service exit timed out. Killing contract 310. ]
> [ Aug 25 13:25:31 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:26:34 Leaving maintenance because clear requested. ]
> [ Aug 25 13:26:34 Enabled. ]
> [ Aug 25 13:26:34 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:27:04 Method or service exit timed out. Killing contract 311. ]
> [ Aug 25 13:27:04 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:31:10 Leaving maintenance because clear requested. ]
> [ Aug 25 13:31:10 Enabled. ]
> [ Aug 25 13:31:10 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:31:40 Method or service exit timed out. Killing contract 313. ]
> [ Aug 25 13:31:40 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:32:39 Leaving maintenance because clear requested. ]
> [ Aug 25 13:32:39 Enabled. ]
> [ Aug 25 13:32:39 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:33:09 Method or service exit timed out. Killing contract 314. ]
> [ Aug 25 13:33:09 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:40:26 Leaving maintenance because disable requested. ]
> [ Aug 25 13:40:26 Disabled. ]
> [ Aug 25 13:49:02 Enabled. ]
> [ Aug 25 13:49:02 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:49:32 Method or service exit timed out. Killing contract 316. ]
> [ Aug 25 13:49:32 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:52:51 Leaving maintenance because clear requested. ]
> [ Aug 25 13:52:51 Enabled. ]
> [ Aug 25 13:52:51 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:53:21 Method or service exit timed out. Killing contract 318. ]
> [ Aug 25 13:53:21 Method "start" failed due to signal KILL. ]
> [ Aug 25 13:58:17 Leaving maintenance because clear requested. ]
> [ Aug 25 13:58:18 Enabled. ]
> [ Aug 25 13:58:18 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 13:58:48 Method or service exit timed out. Killing contract 319. ]
> [ Aug 25 13:58:48 Method "start" failed due to signal KILL. ]
> [ Aug 25 14:00:14 Leaving maintenance because clear requested. ]
> [ Aug 25 14:00:14 Enabled. ]
> [ Aug 25 14:00:14 Executing start method ("/lib/svc/method/ipfilter start"). ]
> [ Aug 25 14:00:45 Method or service exit timed out. Killing contract 322. ]
> [ Aug 25 14:00:45 Method "start" failed due to signal KILL. ]
> --
> This message posted from opensolaris.org
> _______________________________________________
> smf-discuss mailing list
> smf-discuss at opensolaris dot org
_______________________________________________
smf-discuss mailing list
smf-discuss at opensolaris dot org
Tom Whitten
thomas.whitten@sun.com
Re: [smf-discuss] svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Aug 25, 2009 3:32 PM   in response to: Tom Whitten

  Click to reply to this thread Reply

One thing that I forgot to mention. I trussed configd, and it was getting
hammered with requests.

tom

Tom Whitten writes:
> I saw the busy configd problem, but there were also a lot of busy gnome
> processes, which I attribute do
> http://defect.opensolaris.org/bz/show_bug.cgi?id=10002. Once I got gnome
> to quiet down by turning off nautilus and rebooting, everything worked fine.
>
> tom
>
> aric writes:
> > I am having two issues with Nevada b121 and SMF after a Live Upgrade from b120 and I am unsure if they are related.
> >
> > First, svc.configd is running constantly at 8-9% of my CPU (Ultra 20). I have never seen this happen so consistently on prior builds. It is a bit of an issue because this is an underpowered workstation for my needs, I transiently work at 80-90% CPU, so I need all of it.
> >
> > Second, I disabled ipfilter and cannot get it to restart. (I first posted this on security, but noticing the svc.configd activity am posting it here). No amount of 'clear' will help and the log file is not helpful to me.
> >
> > Thank you for any suggestions.
> >
> > % pfexec svcs -l ipfilter
> > fmri svc:/network/ipfilter:default
> > name IP Filter
> > enabled true
> > state maintenance
> > next_state none
> > state_time Tue Aug 25 14:09:33 2009
> > logfile /var/svc/log/network-ipfilter:default.log
> > restarter svc:/system/svc/restarter:default
> > contract_id
> > dependency require_all/none svc:/system/filesystem/minimal (online)
> > dependency require_all/restart svc:/network/physical (multiple)
> > dependency require_all/restart svc:/system/identity:node (online)
> > dependency require_all/restart svc:/system/identity:domain (online)
> >
> > Log file:
> >
> > [ Aug 24 11:51:23 Enabled. ]
> > [ Aug 24 11:51:55 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > Set 0 now inactive
> > filter sync'd
> > 0 entries flushed from NAT table
> > 4 entries flushed from NAT list
> > [ Aug 24 11:52:04 Method "start" exited with status 0. ]
> > [ Aug 25 13:14:16 Stopping because service disabled. ]
> > [ Aug 25 13:14:17 Executing stop method ("/lib/svc/method/ipfilter stop"). ]
> > [ Aug 25 13:14:18 Method "stop" exited with status 0. ]
> > [ Aug 25 13:16:43 Enabled. ]
> > [ Aug 25 13:16:43 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:17:13 Method or service exit timed out. Killing contract 305. ]
> > [ Aug 25 13:17:13 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:17:13 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:17:44 Method or service exit timed out. Killing contract 306. ]
> > [ Aug 25 13:17:44 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:17:44 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:18:14 Method or service exit timed out. Killing contract 307. ]
> > [ Aug 25 13:18:14 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:18:55 Leaving maintenance because disable requested. ]
> > [ Aug 25 13:18:55 Disabled. ]
> > [ Aug 25 13:23:18 Enabled. ]
> > [ Aug 25 13:23:18 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:23:48 Method or service exit timed out. Killing contract 309. ]
> > [ Aug 25 13:23:49 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:25:01 Leaving maintenance because clear requested. ]
> > [ Aug 25 13:25:01 Enabled. ]
> > [ Aug 25 13:25:01 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:25:31 Method or service exit timed out. Killing contract 310. ]
> > [ Aug 25 13:25:31 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:26:34 Leaving maintenance because clear requested. ]
> > [ Aug 25 13:26:34 Enabled. ]
> > [ Aug 25 13:26:34 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:27:04 Method or service exit timed out. Killing contract 311. ]
> > [ Aug 25 13:27:04 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:31:10 Leaving maintenance because clear requested. ]
> > [ Aug 25 13:31:10 Enabled. ]
> > [ Aug 25 13:31:10 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:31:40 Method or service exit timed out. Killing contract 313. ]
> > [ Aug 25 13:31:40 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:32:39 Leaving maintenance because clear requested. ]
> > [ Aug 25 13:32:39 Enabled. ]
> > [ Aug 25 13:32:39 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:33:09 Method or service exit timed out. Killing contract 314. ]
> > [ Aug 25 13:33:09 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:40:26 Leaving maintenance because disable requested. ]
> > [ Aug 25 13:40:26 Disabled. ]
> > [ Aug 25 13:49:02 Enabled. ]
> > [ Aug 25 13:49:02 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:49:32 Method or service exit timed out. Killing contract 316. ]
> > [ Aug 25 13:49:32 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:52:51 Leaving maintenance because clear requested. ]
> > [ Aug 25 13:52:51 Enabled. ]
> > [ Aug 25 13:52:51 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:53:21 Method or service exit timed out. Killing contract 318. ]
> > [ Aug 25 13:53:21 Method "start" failed due to signal KILL. ]
> > [ Aug 25 13:58:17 Leaving maintenance because clear requested. ]
> > [ Aug 25 13:58:18 Enabled. ]
> > [ Aug 25 13:58:18 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 13:58:48 Method or service exit timed out. Killing contract 319. ]
> > [ Aug 25 13:58:48 Method "start" failed due to signal KILL. ]
> > [ Aug 25 14:00:14 Leaving maintenance because clear requested. ]
> > [ Aug 25 14:00:14 Enabled. ]
> > [ Aug 25 14:00:14 Executing start method ("/lib/svc/method/ipfilter start"). ]
> > [ Aug 25 14:00:45 Method or service exit timed out. Killing contract 322. ]
> > [ Aug 25 14:00:45 Method "start" failed due to signal KILL. ]
> > --
> > This message posted from opensolaris.org
> > _______________________________________________
> > smf-discuss mailing list
> > smf-discuss at opensolaris dot org
> _______________________________________________
> smf-discuss mailing list
> smf-discuss at opensolaris dot org
_______________________________________________
smf-discuss mailing list
smf-discuss at opensolaris dot org
tp47565

Posts: 55
From: NZ

Registered: 7/26/09
Re: [smf-discuss] svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Aug 25, 2009 4:59 PM   in response to: aorchid

  Click to reply to this thread Reply


I've seen this straight after an upgrade, but after "a while" it normally settles down.

My advice, leave it alone, if it still doing this after an hour then investigate further.

aric wrote:
<pre wrap="">I am having two issues with Nevada b121 and SMF after a Live Upgrade from b120 and I am unsure if they are related. First, svc.configd is running constantly at 8-9% of my CPU (Ultra 20). I have never seen this happen so consistently on prior builds. It is a bit of an issue because this is an underpowered workstation for my needs, I transiently work at 80-90% CPU, so I need all of it. Second, I disabled ipfilter and cannot get it to restart. (I first posted this on security, but noticing the svc.configd activity am posting it here). No amount of 'clear' will help and the log file is not helpful to me. Thank you for any suggestions. % pfexec svcs -l ipfilter fmri svc:/network/ipfilter:default name IP Filter enabled true state maintenance next_state none state_time Tue Aug 25 14:09:33 2009 logfile /var/svc/log/network-ipfilter:default.log restarter svc:/system/svc/restarter:default contract_id dependency require_all/none svc:/system/filesystem/minimal (online) dependency require_all/restart svc:/network/physical (multiple) dependency require_all/restart svc:/system/identity:node (online) dependency require_all/restart svc:/system/identity:domain (online) Log file: [ Aug 24 11:51:23 Enabled. ] [ Aug 24 11:51:55 Executing start method ("/lib/svc/method/ipfilter start"). ] Set 0 now inactive filter sync'd 0 entries flushed from NAT table 4 entries flushed from NAT list [ Aug 24 11:52:04 Method "start" exited with status 0. ] [ Aug 25 13:14:16 Stopping because service disabled. ] [ Aug 25 13:14:17 Executing stop method ("/lib/svc/method/ipfilter stop"). ] [ Aug 25 13:14:18 Method "stop" exited with status 0. ] [ Aug 25 13:16:43 Enabled. ] [ Aug 25 13:16:43 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:17:13 Method or service exit timed out. Killing contract 305. ] [ Aug 25 13:17:13 Method "start" failed due to signal KILL. ] [ Aug 25 13:17:13 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:17:44 Method or service exit timed out. Killing contract 306. ] [ Aug 25 13:17:44 Method "start" failed due to signal KILL. ] [ Aug 25 13:17:44 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:18:14 Method or service exit timed out. Killing contract 307. ] [ Aug 25 13:18:14 Method "start" failed due to signal KILL. ] [ Aug 25 13:18:55 Leaving maintenance because disable requested. ] [ Aug 25 13:18:55 Disabled. ] [ Aug 25 13:23:18 Enabled. ] [ Aug 25 13:23:18 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:23:48 Method or service exit timed out. Killing contract 309. ] [ Aug 25 13:23:49 Method "start" failed due to signal KILL. ] [ Aug 25 13:25:01 Leaving maintenance because clear requested. ] [ Aug 25 13:25:01 Enabled. ] [ Aug 25 13:25:01 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:25:31 Method or service exit timed out. Killing contract 310. ] [ Aug 25 13:25:31 Method "start" failed due to signal KILL. ] [ Aug 25 13:26:34 Leaving maintenance because clear requested. ] [ Aug 25 13:26:34 Enabled. ] [ Aug 25 13:26:34 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:27:04 Method or service exit timed out. Killing contract 311. ] [ Aug 25 13:27:04 Method "start" failed due to signal KILL. ] [ Aug 25 13:31:10 Leaving maintenance because clear requested. ] [ Aug 25 13:31:10 Enabled. ] [ Aug 25 13:31:10 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:31:40 Method or service exit timed out. Killing contract 313. ] [ Aug 25 13:31:40 Method "start" failed due to signal KILL. ] [ Aug 25 13:32:39 Leaving maintenance because clear requested. ] [ Aug 25 13:32:39 Enabled. ] [ Aug 25 13:32:39 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:33:09 Method or service exit timed out. Killing contract 314. ] [ Aug 25 13:33:09 Method "start" failed due to signal KILL. ] [ Aug 25 13:40:26 Leaving maintenance because disable requested. ] [ Aug 25 13:40:26 Disabled. ] [ Aug 25 13:49:02 Enabled. ] [ Aug 25 13:49:02 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:49:32 Method or service exit timed out. Killing contract 316. ] [ Aug 25 13:49:32 Method "start" failed due to signal KILL. ] [ Aug 25 13:52:51 Leaving maintenance because clear requested. ] [ Aug 25 13:52:51 Enabled. ] [ Aug 25 13:52:51 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:53:21 Method or service exit timed out. Killing contract 318. ] [ Aug 25 13:53:21 Method "start" failed due to signal KILL. ] [ Aug 25 13:58:17 Leaving maintenance because clear requested. ] [ Aug 25 13:58:18 Enabled. ] [ Aug 25 13:58:18 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 13:58:48 Method or service exit timed out. Killing contract 319. ] [ Aug 25 13:58:48 Method "start" failed due to signal KILL. ] [ Aug 25 14:00:14 Leaving maintenance because clear requested. ] [ Aug 25 14:00:14 Enabled. ] [ Aug 25 14:00:14 Executing start method ("/lib/svc/method/ipfilter start"). ] [ Aug 25 14:00:45 Method or service exit timed out. Killing contract 322. ] [ Aug 25 14:00:45 Method "start" failed due to signal KILL. ] </pre>

--
<meta http-equiv="CONTENT-TYPE" content="text/html; "> <title></title> <meta name="GENERATOR" content="OpenOffice.org 3.1 (Win32)"> <meta name="CREATED" content="20090703;14253500"> <meta name="CHANGED" content="20090818;12220100">

Trevor Pretty | Technical Account Manager | +64 9 639 0652 | +64 21 666 161
Eagle Technology Group Ltd.
Gate D, Alexandra Park, Greenlane West, Epsom
Private Bag 93211, Parnell, Auckland

www.eagle.co.nz 

This email is confidential and may be legally privileged. If received in error please destroy and immediately notify us.

_______________________________________________ smf-discuss mailing list smf-discuss at opensolaris dot org

aorchid

Posts: 109
From: US

Registered: 9/22/06
Re: [smf-discuss] svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Aug 25, 2009 5:44 PM   in response to: tp47565

  Click to reply to this thread Reply

Trevor Pretty wrote:
>
> My advice, leave it alone, if it still doing this after an hour then
> investigate further.

Thanks. I did try this approach before reporting it. The machine had
been running for over 48 hours.

aric
_______________________________________________
smf-discuss mailing list
smf-discuss at opensolaris dot org
markdr

Posts: 2
From:

Registered: 6/17/05
Re: [smf-discuss] svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Aug 31, 2009 2:40 PM   in response to: aorchid
To: Communities » smf » discuss
  Click to reply to this thread Reply

I recently updated my OpenSolaris (Indiana) to build 121 from 118 and started having the same issue.

I found that the desktop print monitoring applet was causing my svc.configd to run like this, I have disabled it and things seem to have settled down.

Mark

benaud

Posts: 9
From: AU

Registered: 3/3/08
Re: [smf-discuss] svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Sep 2, 2009 11:06 PM   in response to: markdr
To: Communities » smf » discuss
Cc: OpenSolaris » arc
  Click to reply to this thread Reply

just for the record, I saw exactly the same behaviour after updating from snv_118 > snv_121 using update manager -- there were no errors during the upgrade

(one small error during boot: the already posted bug: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6860272)

After first reboot/login, svc.configd sat steadily on 18% CPU usage and desktop-print-management-applet at 5% CPU usage ..

I disabled Desktop Printing Monitoring applet in the Startup Application preferences and the problem disappeared.

Regards,
Ben

iban

Posts: 160
From: ES

Registered: 9/30/05
Re: [smf-discuss] svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Sep 4, 2009 2:14 PM   in response to: benaud
To: Communities » smf » discuss
  Click to reply to this thread Reply

Thank you, I have fixed the problem too :)

Kill this process and the CPU is now working in normal behaviour:
/usr/perl5/bin/perl /usr/bin/desktop-print-management-applet

Dont start it from GNOME!

Regards

paul_a_j

Posts: 92
From: GB

Registered: 5/7/08
Re: [smf-discuss] svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Sep 6, 2009 3:38 AM   in response to: iban
To: Communities » smf » discuss
  Click to reply to this thread Reply

This seems to affect Indiana as well
SunOS opensolaris-home 5.11 snv_122 i86pc i386 i86pc Solaris

PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
9 root 13M 12M cpu0 49 0 0:49:31 22% svc.configd/24
14842 louis 9204K 2516K run 20 0 0:00:27 3.9% desktop-print-m/1
3364 louise 9204K 2568K run 20 0 0:04:12 3.7% desktop-print-m/1

Users louis and louise are no longer logged on:

paulj@opensolaris-home:~$ who
paulj console 2009-09-06 11:33 (:0)
paulj pts/2 2009-09-06 11:33 (:0.0)
paulj pts/3 2009-09-06 11:34 (:0.0)


Regards Paul

gheet

Posts: 815
From: IE

Registered: 6/15/05
Re: svc.configd running 9% CPU constant after LU b120->b121 Nevada
Posted: Sep 8, 2009 1:46 AM   in response to: aorchid
To: Communities » smf » discuss
  Click to reply to this thread Reply

This is bug http://defect.opensolaris.org/bz/show_bug.cgi?id=10863
see bug for a fix, http://defect.opensolaris.org/bz/show_bug.cgi?id=10863#c10


Point your RSS reader here for a feed of the latest messages in all forums
Go Back Back to Thread List



Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2005 Sun Microsystems, Inc.