Cron service in maintenance mode
Hi Experts,
I need an advice how to bring cron service online. It's in maintenance mode all the time and when I try to enable it, I'm keep getting below errors in log file, and service stays in maintenance mode:
[ Apr 22 07:58:48 Stopping because all processes in service exited. ]
[ Apr 22 07:58:48 Executing stop method (:kill) ]
[ Apr 22 07:58:48 Executing start method ("/lib/svc/method/svc-cron") ]
[ Apr 22 07:58:48 Method "start" exited with status 0 ]
cron could not unlink FIFO: No such file or directory
! cannot create fifo queue Mon Apr 22 07:58:48 2013
! ******* CRON ABORTED ******** Mon Apr 22 07:58:48 2013
[ Apr 22 07:58:48 Stopping because all processes in service exited. ]
[ Apr 22 07:58:48 Executing stop method (:kill) ]
[ Apr 22 07:58:48 Restarting too quickly, changing state to maintenance ]
I was searching for that errors and I found that this may be caused by missing FIFO file in /etc/cron.d directory but when I tried to make it by mknod i get this error:
/usr/sbin/mknod /var/adm/cron/FIFO p
mknod: No such device
I'm not even sure if this is correct direction of root cause but I'm stuck at this point and need your help. If anybody experienced such issue, please advice.
System details:
uname -a
SunOS lspz1215 5.10 Generic_147440-01 sun4v sparc SUNW,SPARC-Enterprise-T5220
Regards,
Wojciech
Hi,
Check that below files exist and have correct permissions:
root@sol10vm#cd /etc/cron.d/
root@sol10vm#ls
FIFO at.deny cron.deny queuedefs
root@sol10vm#ls -ltr
total 6
-rw-r--r-- 1 root sys 17 Jan 22 2005 queuedefs
-rw-r--r-- 1 root sys 40 Jan 11 21:35 cron.deny
-rw-r--r-- 1 root sys 40 Jan 11 21:35 at.deny
prw------- 1 root root 0 Apr 22 13:04 FIFO
root@sol10vm#file FIFO
FIFO: fifo
root@sol10vm#pwd
/etc/cron.d
root@sol10vm#ls -ld /etc/cron.d
drwxr-xr-x 2 root sys 512 Apr 22 13:04 /etc/cron.d
root@sol10vm#
after you correct them, issue 'svcadm -v clear cron'
Regards,
Rei
Similar Messages
-
Powershell script for put the particular service in to Maintenance mode
Hi Everyone,
I have requinquent to schedule the Maintenance mode for service. If anyone help with script to put the service into maintenance mode, then i can schedule the same through Task Scheduler.
Thanks in advance.
Regards
KarthickHi,
Please have a look on:
http://technet.microsoft.com/en-us/library/hh918505(v=sc.20).aspx
http://blog.coretech.dk/msk/operations-manager-2012-maintenance-mode/
Cheers
Christoph Maresch | My blogs: blog.cmaresch.at | XING:
Christoph Maresch
| Linkedin:
Christoph Maresch -
All services stuck in maintenance mode
I've got a problem on Solaris 10. All of the enabled inet services are in maintenance mode. rlogin, ftp, telnet, stlisten, xfs, etc, etc - are all in maintenance mode. The inetadm command shows no online services, only disabled and maintenance. I've tried clearing them with svcadm but they won't clear. It won't show any explanation for why.
What could be wrong to cause this?
Thanks for any suggestions.
RandyThanks very much for the very helpful suggestions. svcs -xv does not show anything helpful - for the Reason, simply "Restarter gave no explanation". The svc:/network/inetd:default is indeed enabled and healthy.
/var/adm/messages, however, has information that might point to the problem. Regrettably, I don't understand the message and am hoping someone here can enlighten me. For each of the services that is in maintenance mode, these messages appear:
Nov 3 17:59:44 trsun006 inetd[322]: [ID 702911 daemon.error] Property exec for method inetd_start of instance svc:/network/login:rlogin is invalid
Nov 3 17:59:44 trsun006 inetd[322]: [ID 702911 daemon.error] Invalid configuration for instance svc:/network/login:rlogin, placing in maintenance
I don't understand what it means by "Property exec for method inetd_start ... is invalid".
I issued these commands-
[trsun006 27] sbin > inetadm -l rlogin | grep exec
exec="/usr/sbin/in.rlogind"
[trsun006 28] sbin > ls -l /usr/sbin/in.rlogind
-r-xr-xr-x 1 root bin 36372 Jan 22 2005 /usr/sbin/in.rlogind*
How can I debug this problem?
Randy -
Services in maintenance or offline mode
Hi,
when I try to open console of solaris 10 on SF V240, it shows maintenance mode and asks for root password. I log in as root but then I do not know what to do,
It also shows message on cosole, console-service not running ..
Where as users are able to connect using ssh and even after trying init 3,
who -r displays following,
run-level Sep 11 15:58 last=
For console-service message , I checked svcs and following 3 are listed as last 3 lines,
maintenance Sep_11 svc:/platform/sun4u/sf880drd:default
maintenance Nov_29 svc:/system/console-login:default
maintenance 14:23:51 svc:/system/auditd:default
svcs -l console-login
fmri svc:/system/console-login:default
name Console login
enabled true
state maintenance
next_state none
state_time Thu Nov 29 14:30:44 2007
logfile /var/svc/log/system-console-login:default.log
restarter svc:/system/svc/restarter:default
contract_id
dependency require_all/none svc:/system/filesystem/minimal (online)
dependency require_all/none svc:/system/identity:node (online)
dependency require_all/none svc:/system/utmp:default (online)
dependency require_all/none svc:/milestone/sysconfig (online)
dependency optional_all/none svc:/system/auditd (maintenance)
I don't know how to get these services running now,
I tried init 3 and it makes no difference,
when I diable and enable the console-login it shows
offline
16:15:29 svc:/system/console-login:default
and
cat /var/svc/log/system-console-login:default.log
-[ Dec 18 16:09:56 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:09:57 Stopping because all processes in service exited. ]
[ Dec 18 16:09:57 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:09:57 Stopping because all processes in service exited. ]
[ Dec 18 16:09:57 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:09:58 Stopping because all processes in service exited. ]
[ Dec 18 16:09:58 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:09:58 Stopping because all processes in service exited. ]
[ Dec 18 16:09:58 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:09:59 Stopping because all processes in service exited. ]
[ Dec 18 16:09:59 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:09:59 Stopping because all processes in service exited. ]
[ Dec 18 16:09:59 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:10:00 Stopping because all processes in service exited. ]
[ Dec 18 16:10:00 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:10:00 Stopping because all processes in service exited. ]
[ Dec 18 16:10:00 Executing start method ("/lib/svc/method/console-login") ]
[ Dec 18 16:10:01 Stopping because all processes in service exited. ]
[ Dec 18 16:10:01 Restarting too quickly, changing state to maintenance ]
[ Dec 18 16:15:20 Leaving maintenance because disable requested. ]
[ Dec 18 16:15:20 Disabled. ]
[ Dec 18 16:15:29 Enabled. ]
/var/log/messages
Dec 18 15:59:41 babbage svc.startd[7]: [ID 748625 daemon.error] system/console-login:default failed repeatedly
I do not want to reboot until we try something,
Could this be related to milestone or multiuser something, I am not aware of above terms but I think this problem could have been caused some time back while I was doing something on console and I remember something of multiuser or milestone message on console..
I am sure there would be some work around than reboot
Please help, I want to maintain runlevel 3 and possibly without a reboot\
Thankswho -r
run-level Sep 11 15:58 last=
uptime
11:01am up 98 days 20:02, 2 users, load average: 1.02, 1.02, 1.04
Actually all services are running like nis and nfs properly and all can login using ssh remotely, system is not rebooted that I am seeing this maintenance root password message,
when I killed sulogin process , then console-login seemed to go online but then again went to maintenance mode.. -
Looking for a Powershell Script which can put the scom servers in maintenance mode
Looking for a Powershell Script which can put the scom servers in maintenance mode so that SCOM should not send an alert during planned task.
Rahul1. Provide list of servers line-by-line in C:\ServerList.txt, make sure you provide limited no. of servers, do not exceed 20 - 25 per batch
2. Save the script with suitable name (test.ps1)
3. Open PowerShell cmd prompt
4. Script accepts 3 params - TimeInMinutes, Reason and Comment
**** Please note, this script will work for SCOM 2012 R2
param([int32]$TimeMin, [string]$Reason, [string]$Comment)
try
$api = new-object -comObject 'MOM.ScriptAPI'
Import-Module operationsmanager
New-SCOMManagementGroupConnection
$Servers = Get-Content "C:\ServerList.txt"
$Time = (Get-Date).Addminutes($TimeMin)
Foreach ($Server in $Servers)
#Get Computer instance
$ComputerClass = Get-SCOMClass -Name Microsoft.Windows.Computer
$ComputerClassInstance = Get-SCOMClassInstance -Class $ComputerClass | Where {$_.DisplayName -eq $Server}
If ($ComputerClassInstance -ne $Null)
$HealthServiceWatcherClass = Get-SCOMClass -name:Microsoft.SystemCenter.HealthServiceWatcher
#Get Health Service Watcher Class instance of the server
$HSWClass = Get-SCOMClass -Name Microsoft.SystemCenter.HealthServiceWatcher
$HSWClassIns = Get-SCOMClassInstance -Class $HSWClass | Where {$_.DisplayName -eq $Server}
#Starting the maintenance mode
Start-SCOMMaintenanceMode -Instance $HSWClassIns -EndTime $Time -Reason $Reason -Comment $Comment
Start-SCOMMaintenanceMode -Instance $ComputerClassInstance -EndTime $Time -Reason $Reason -Comment $Comment
Write-Host "Health Service Watcher and Agent server "$Server " kept in maintenance mode" -foregroundcolor "green"
$api.LogScriptEvent('MaintenanceModeScript.ps1', 200, 0, "$Server kept in maintenance mode for $TimeMin minutes")
Else
Write-Host $Server" not found " -foregroundcolor "red"
$api.LogScriptEvent('MaintenanceModeScript.ps1', 201, 1, "$Server could not be found in domain")
Catch [system.exception]
$api.LogScriptEvent('MaintenanceModeScript.ps1', 201, 1, $_.Exception.Message)
Faizan -
SQL Query for maintenance mode in SCOM
Hi all
I was wondering if I can find a query about this request:
- Found all the Servers that were restart without the maintenance mode were actived ?
It's to make a Report To include in Reporting Services.
sorry for my English :)
Thank you very much and have a good dayYour question seems related to SCOM. SCOM may use SQL Server, but to answer the question, I guess one needs to know SCOM, so maybe you should try a forum for that product? I found
http://social.technet.microsoft.com/Forums/systemcenter/en-US/home?forum=operationsmanagergeneral
Erland Sommarskog, SQL Server MVP, [email protected] -
Solaris 10 disk mirror partition goes in maintenance mode at reboot
Hello
I have got solaris 10 installed on a Sun machine with 2 disks mirrorred to each other. There also security toolkit 4.2 installed. Now every time the system reboots and I do a metastat the mirror partitions goes in maintenance mode and I have to individually metasync the mirrors after every reboot.
I guess this due to the security toolkit playing up. Would really appreciate any help to sort this out. The mirrors should automatically resync after system reboot.
Thanks in advance.
PioneerHi yes I did run the metaroot. If I manually metasync its all OK. My problem is the partition does not auto sync after the system boots.
I guess this is someting to do with the security toolkit 4.2 playing up not disabling some services at boot. Have any one faced this issue ?
Many Thanks
Pioneer -
Failed to get Monitor - Start Maintenance Mode
Hi,
Am struggling with a problem with Orchestrator R2 apparently not recognising output from a Monitor alert step in a run book. I have Orchestrator 2012R2 and SCOM 2012R2 configured. Orchestrator is co-located with VMM2012R2.
Operating system for all is Windows server 2012
I have installed and deployed the Orchestrator R2 Integration packs which in deployment manager state version 7.2
I have checked to ensure that both Orchestrator, SCOM and VMM are all R2 (They are)
I am looking to create a runbook that will start services as per the link here: (Thanks to Jakob for this)
http://blog.coretech.dk/jgs/sco-2012-scom-2012-best-practice-monitor-alert-and-restart-a-service/
I can test the connection to the SCOM server - fine
I create the monitor alert step and test - fine
I create the start maintenance mode step and get the following error:
Filed to get Monitor. The exception was "An object of class MonitoringObject with ID 00000000-0000-0000-0000-000000000000 was not found.".
I have used the runbook tester and the monitoringobjectfullname is present in the output for the start maintenance mode step.
However irrespective of the variable that I attempt to use in start maintenance mode step I continue to get the same error as above.
The monitor alert step completes with no issues, but everytime on the start maint mode step it fails.
I have validated the SCOM connection account has all the appropriate SCOM permissions. I have also provided it with full domain admin rights, but with no success.
Any ideas on how to troubleshoot this would be welcomed
Thanks in advanceHi Stefan,
A little extension of your approach as this is only usable if you want to set a Windows Server into Maintenance Mode - but not e.g. for Distributed Apps
I just required the "Start Maintenance Mode" Activity to set a distributed app and a websphere application server instance (which is not linked with the server itself). And I did not find any documentation how to fill the field - only for Windows
Computer.
So I'll post my result on how to get the value which needs to be entered within the "Monitor" field:
(PowerShell - Use "Activities > System > Run .Net Script > Type: Powershell)
Import-Module OperationsManager
$object= Get-SCOMMonitoringObject -displayname "<desired object displayname";
# or use the ID instead:
# $object = Get-SCOMMonitoringObject -ID "<ID of object>";
$name = $object.displayname;
$fullname = $object.fullname;
$monitor = $name + " : " + $fullname
Then put $monitor within "published data" and you can use it directly in the "Start Maintenance Mode" Activity.
This only works if the runbook is running on a SCOM management server as it requires the SCOM Powershell Module. But at least it somehow shows the syntax.
Best Regards
Klaus
Austria -
Some services in maintenance state after reboot
Hi,
I installed solaris 10 and everything ran fine for a month. I recently upgraded memory on the server and when I rebooted, some of the services were put in the maintenance mode.
Here is the solaris 10 release info:
bash-3.00# cat /etc/release
Solaris 10 1/06 s10s_u1wos_19a SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 December 2005
Here is the error during boot up
irvsun12 console login: Mar 2 11:20:42 inetd[230]: Property 'name' of instance svc:/network/rpc/rstat:default is missing, inconsistent or invalid
Mar 2 11:20:42 inetd[230]: Invalid configuration for instance svc:/network/rpc/rstat:default, placing in maintenance
Mar 2 11:20:42 inetd[230]: Property 'name' of instance svc:/network/rpc/rusers:default is missing, inconsistent or invalid
Mar 2 11:20:42 inetd[230]: Invalid configuration for instance svc:/network/rpc/rusers:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/telnet:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/telnet:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'name' of instance svc:/network/nfs/rquota:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/nfs/rquota:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/ftp:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/ftp:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/finger:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/finger:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/login:rlogin is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/login:rlogin, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/shell:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/shell:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/application/x11/xfs:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/application/x11/xfs:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/application/print/rfc1179:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/application/print/rfc1179:default, placing in maintenance
Any help on getting this resolved is appreciated.
ThanksI have run into the same problem and cannot figure out how to resolve it.
Here is what I saw during the boot process:
May 11 21:37:59 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/gss:default is invalid
May 11 21:37:59 inetd[202]: Invalid configuration for instance svc:/network/rpc/gss:default, placing in maintenance
May 11 21:38:01 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/mdcomm:default is invalid
May 11 21:38:01 inetd[202]: Invalid configuration for instance svc:/network/rpc/mdcomm:default, placing in maintenance
May 11 21:38:01 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/meta:default is invalid
May 11 21:38:01 inetd[202]: Invalid configuration for instance svc:/network/rpc/meta:default, placing in maintenance
May 11 21:38:02 svc.startd[7]: svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" failed with exit status 1.
May 11 21:38:02 svc.startd[7]: svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" failed with exit status 1.
May 11 21:38:02 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/metamed:default is invalid
May 11 21:38:02 svc.startd[7]: svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" failed with exit status 1.
May 11 21:38:02 inetd[202]: Invalid configuration for instance svc:/network/rpc/metamed:default, placing in maintenance
May 11 21:38:02 svc.startd[7]: system/mdmonitor:default failed
May 11 21:38:03 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/metamh:default is invalid
May 11 21:38:04 inetd[202]: Invalid configuration for instance svc:/network/rpc/metamh:default, placing in maintenance
May 11 21:38:04 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/rstat:default is invalid
May 11 21:38:04 inetd[202]: Invalid configuration for instance svc:/network/rpc/rstat:default, placing in maintenance
May 11 21:38:05 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/rusers:default is invalid
May 11 21:38:05 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc/rusers:default, placing in maintenance
May 11 21:38:06 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/security/ktkt_warn:default is invalid
May 11 21:38:06 louise2 inetd[202]: Invalid configuration for instance svc:/network/security/ktkt_warn:default, placing in maintenance
May 11 21:38:06 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/telnet:default is invalid
May 11 21:38:06 louise2 inetd[202]: Invalid configuration for instance svc:/network/telnet:default, placing in maintenance
May 11 21:38:07 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/nfs/rquota:default is invalid
May 11 21:38:07 louise2 inetd[202]: Invalid configuration for instance svc:/network/nfs/rquota:default, placing in maintenance
May 11 21:38:08 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/ftp:default is invalid
May 11 21:38:08 louise2 inetd[202]: Invalid configuration for instance svc:/network/ftp:default, placing in maintenance
May 11 21:38:08 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/finger:default is invalid
May 11 21:38:08 louise2 inetd[202]: Invalid configuration for instance svc:/network/finger:default, placing in maintenance
May 11 21:38:09 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/login:rlogin is invalid
May 11 21:38:09 louise2 inetd[202]: Invalid configuration for instance svc:/network/login:rlogin, placing in maintenance
May 11 21:38:09 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/shell:default is invalid
May 11 21:38:09 louise2 inetd[202]: Invalid configuration for instance svc:/network/shell:default, placing in maintenance
May 11 21:38:09 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/application/font/stfsloader:default is invalid
May 11 21:38:09 louise2 inetd[202]: Invalid configuration for instance svc:/application/font/stfsloader:default, placing in maintenance
May 11 21:38:09 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/application/x11/xfs:default is invalid
May 11 21:38:09 louise2 inetd[202]: Invalid configuration for instance svc:/application/x11/xfs:default, placing in maintenance
May 11 21:38:10 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc/smserver:default is invalid
May 11 21:38:10 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc/smserver:default, placing in maintenance
May 11 21:38:10 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/application/print/rfc1179:default is invalid
May 11 21:38:10 louise2 inetd[202]: Invalid configuration for instance svc:/application/print/rfc1179:default, placing in maintenance
May 11 21:38:10 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc-100235_1/rpc_ticotsord:default is invalid
May 11 21:38:10 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc-100235_1/rpc_ticotsord:default, placing in maintenance
May 11 21:38:11 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc-100083_1/rpc_tcp:default is invalid
May 11 21:38:11 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc-100083_1/rpc_tcp:default, placing in maintenance
May 11 21:38:11 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/rpc-100068_2-5/rpc_udp:default is invalid
May 11 21:38:11 louise2 inetd[202]: Invalid configuration for instance svc:/network/rpc-100068_2-5/rpc_udp:default, placing in maintenance
May 11 21:38:11 louise2 inetd[202]: Property exec for method inetd_start of instance svc:/network/tftp/udp6:default is invalid
May 11 21:38:11 louise2 inetd[202]: Invalid configuration for instance svc:/network/tftp/udp6:default, placing in maintenance
And if I run: svcprop rpc/gss:default
general/enabled boolean true
general/entity_stability astring Unstable
general/restarter fmri svc:/network/inetd:default
rpcbind/entities fmri svc:/network/rpc/bind
rpcbind/grouping astring require_all
rpcbind/restart_on astring restart
rpcbind/type astring service
keyserv/entities fmri svc:/network/rpc/keyserv
keyserv/grouping astring optional_all
keyserv/restart_on astring none
keyserv/type astring service
inetd/endpoint_type astring tli
inetd/isrpc boolean true
inetd/name astring 100234
inetd/proto astring ticotsord
inetd/rpc_high_version integer 1
inetd/rpc_low_version integer 1
inetd/stability astring Evolving
inetd/wait boolean true
inetd_start/exec astring /usr/lib/gss/gssd
inetd_start/group astring root
inetd_start/limit_privileges astring :default
inetd_start/privileges astring basic,!file_link_any,!proc_info,!proc_session,net_privaddr,file_chown,file_dac_read,file_dac_write
inetd_start/project astring :default
inetd_start/resource_pool astring :default
inetd_start/supp_groups astring :default
inetd_start/timeout_seconds count 0
inetd_start/type astring method
inetd_start/use_profile boolean false
inetd_start/user astring root
inetd_start/working_directory astring :default
inetd_offline/exec astring :kill_process
inetd_offline/timeout_seconds count 0
inetd_offline/type astring method
inetd_disable/exec astring :kill
inetd_disable/timeout_seconds count 0
inetd_disable/type astring method
tm_common_name/C ustring Generic\ Security\ Service
tm_man_gssd/manpath astring /usr/share/man
tm_man_gssd/section astring 1M
tm_man_gssd/title astring gssd
restarter/auxiliary_state astring none
restarter/next_state astring none
restarter/state astring maintenance
restarter/state_timestamp time 1147397880.430382000
inetd_state/cur_state integer 8
inetd_state/next_state integer 13
# -
Some services in maintenance after reboot
Hi,
I installed solaris 10 and everything ran fine for a month. I recently upgraded memory on the server and when I rebooted, some of the services were put in the maintenance mode.
Here is the solaris 10 release info:
bash-3.00# cat /etc/release
Solaris 10 1/06 s10s_u1wos_19a SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 December 2005
Here is the error during boot up
irvsun12 console login: Mar 2 11:20:42 inetd[230]: Property 'name' of instance svc:/network/rpc/rstat:default is missing, inconsistent or invalid
Mar 2 11:20:42 inetd[230]: Invalid configuration for instance svc:/network/rpc/rstat:default, placing in maintenance
Mar 2 11:20:42 inetd[230]: Property 'name' of instance svc:/network/rpc/rusers:default is missing, inconsistent or invalid
Mar 2 11:20:42 inetd[230]: Invalid configuration for instance svc:/network/rpc/rusers:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/telnet:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/telnet:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'name' of instance svc:/network/nfs/rquota:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/nfs/rquota:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/ftp:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/ftp:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/finger:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/finger:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/login:rlogin is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/login:rlogin, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/network/shell:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/network/shell:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/application/x11/xfs:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/application/x11/xfs:default, placing in maintenance
Mar 2 11:20:43 inetd[230]: Property 'proto' of instance svc:/application/print/rfc1179:default is missing, inconsistent or invalid
Mar 2 11:20:43 inetd[230]: Invalid configuration for instance svc:/application/print/rfc1179:default, placing in maintenance
Any help on getting this resolved is appreciated.
ThanksMany thanks hubery.
I had mutiple svc network service errors or warnings when re-booting a Solaris 10 x86 10/09 u8 after adding the box to MS Active Directory using adjoin.sh as per the paper written by Wajih Ahmed and Baban Kenre (Thanks for the notes guys by the way, mines working against 2003 with no service pack after installing SFU(Services For Unix)).
I'd also installed the Dec. 09 patch bundle to no avail. Thank goodness we don't get those meaningless patch errors now, just 'skipped' or 'success'.
The nsswitch.conf file looked like this.
networks: ldap [NOTFOUND=return] files
protocols: ldap [NOTFOUND=return] files
rpc: ldap [NOTFOUND=return] files
ethers: ldap [NOTFOUND=return] files
netmasks: ldap [NOTFOUND=return] files
bootparams: ldap [NOTFOUND=return] files
publickey: ldap [NOTFOUND=return] files
After removing the [NOTFOUND=return] section on each line the warnings no longer appear on boot, yay.
Here's the complete working nsswitch.conf file:
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# ident "@(#)nsswitch.ldap 1.10 06/05/03 SMI"
# /etc/nsswitch.ldap:
# An example file that could be copied over to /etc/nsswitch.conf; it
# uses LDAP in conjunction with files.
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.
# LDAP service requires that svc:/network/ldap/client:default be enabled
# and online.
# the following two lines obviate the "+" entry in /etc/passwd and /etc/group.
passwd: files ldap
group: files ldap
# consult /etc "files" only if ldap is down.
hosts: dns files
# Note that IPv4 addresses are searched for in all of the ipnodes databases
# before searching the hosts databases.
ipnodes: dns files
networks: ldap files
protocols: ldap files
rpc: ldap files
ethers: ldap files
netmasks: ldap files
bootparams: ldap files
publickey: ldap files
netgroup: ldap
automount: files ldap
aliases: files ldap
# for efficient getservbyname() avoid ldap
services: files ldap
printers: user files ldap
auth_attr: files ldap
prof_attr: files ldap
project: files ldap
tnrhtp: files ldap
tnrhdb: files ldap -
OVM-2020 Server pool master can not be set to maintenance mode
Hi Guys.
I have 2 server in ha mode
server 1 (10.99.99.161) with oracle Manager installed (server pool master, utility server, vm server)
Server 2 (10.99.99.161) without Oracle Manager installed (utility server, vmserver)
HA enable with server1 and server 2
10.99.99.165 is the virtual server pool master
1 San connected with server 1 and server 2.
Without problem I can connect on https://10.99.99.165:4443/OVS without problem.
All seems work, but :
1 - I I try to set in maintenance mode the server 1, the VM Manager say me:
OVM-2020 Server pool master (10.99.99.162) can not be set to maintenance mode, please use server pool master failover policy to change its role, then try again.
What I shuld do ?
2 - If I turn off the server 1 the server pool master is attribuite to server 2, but I'm unable to connect on https://10.99.99.165:4443/OVS webpage. It is correct, it is a bug, or I'm doing something wrong ? Must I upgrate something ?
Many Thanks
Lucauser8857532 wrote:
1 - I I try to set in maintenance mode the server 1, the VM Manager say me:
What I shuld do ?You need to live migrate all your guests off the current Master server, then issue service ovs-agent stop on the command-line. This will cause the pool mastery to switch to another server. Once that's done, you can start the agent agent.
2 - If I turn off the server 1 the server pool master is attribuite to server 2, but I'm unable to connect on https://10.99.99.165:4443/OVS webpage. It is correct, it is a bug, or I'm doing something wrong ? Must I upgrate something ?
You need to ensure the VM that's running the Oracle VM Manager software is still running. Live Migrate it first (preferred option) and flag it HA-enabled so that it is automatically restarted in the case of a server failure. -
We have 2 wlc 5508 with software 7.5.102.0, both wlc have 25 AP license.
We try to setup HA SSO but 1 wlc in maintenance mode: Maintenance cause= Incompatible Software license
Could you help me ?
thanks.
============== Primary controller===========================
(Cisco Controller) >show redundancy summary
Redundancy Mode = SSO ENABLED
Local State = ACTIVE
Peer State = UNKNOWN - Communication Down
Unit = Primary
Unit ID = BC:16:65:F9:19:60
Redundancy State = Non Redundant
Mobility MAC = BC:16:65:F9:19:60
Redundancy Management IP Address................. 192.168.11.11
Peer Redundancy Management IP Address............ 192.168.11.12
Redundancy Port IP Address....................... 169.254.11.11
Peer Redundancy Port IP Address.................. 169.254.11.12
(Cisco Controller) >
(Cisco Controller) >show interface summary
Number of Interfaces.......................... 5
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
management LAG 30 192.168.11.9 Static Yes No
redundancy-management LAG 30 192.168.11.11 Static No No
redundancy-port - untagged 169.254.11.11 Static No No
service-port N/A N/A 0.0.0.0 DHCP No No
virtual N/A N/A 1.1.1.1 Static No No
============== Secondary controller===========================
(Cisco Controller) >show redundancy summary
Redundancy Mode = SSO ENABLED
Local State = MAINTENANCE
Peer State = UNKNOWN - Communication Down
Unit = Primary
Unit ID = F8:72:EA:EE:86:60
Redundancy State = Non Redundant
Mobility MAC = F8:72:EA:EE:86:60
Maintenance Mode = Enabled
Maintenance cause= Incompatible Software license
Redundancy Management IP Address................. 192.168.11.12
Peer Redundancy Management IP Address............ 192.168.11.11
Redundancy Port IP Address....................... 169.254.11.12
Peer Redundancy Port IP Address.................. 169.254.11.11
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >show interface sum
Number of Interfaces.......................... 5
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
management LAG 30 192.168.11.10 Static Yes No
redundancy-management LAG 30 192.168.11.12 Static No No
redundancy-port - untagged 169.254.11.12 Static No No
service-port N/A N/A 0.0.0.0 DHCP No No
virtual N/A N/A 1.1.1.1 Static No NoIn order to use a WLC that has a license as an HA WLC, you need a minimum of a 50 AP license.
http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bd3504.shtml
If you want to convert any existing WLC as a Standby WLC, do so using the config redundancy unit secondary command in the CLI. This CLI command will only work if the WLC which is intended to work as Standby has some number of permanent license count. This condition is only valid for the 5500 WLC, where a minimum of 50 AP Permanent licenses are needed to be converted to Standby. There is no restriction for other WLCs such as the WiSM2, 7500, and 8500.
Sent from Cisco Technical Support iPhone App -
SCOM 2012 Maintenance Mode PowerShell Script Problems
I've seen other questions about this topic before, but none of them seem to address my specific problem, so I am starting a new thread.
I am writing a script to put a single server (not a group) into maintenance mode. Here is the command that it ultimately tries to call:
Start-SCOMMaintenanceMode-Instance$Instance-EndTime$EndTime-Reason$Reason-Comment$Comment
So an exmaple would look like this:
Start-SCOMMaintenanceMode -Instance "$Instance -EndTime "02/03/2014 15:26:00" -Reason "PlannedOther" -Comment "Testing Maintenance Mode"
When my script tries to run this command, this is the error message that I get:
Start-SCOMMaintenanceMode : Start time must be before end time for maintenance mode.
Parameter name: startTime
At C:\users\x036036\Desktop\Start-SCOMMaintenanceModeForServer.ps1:143 char:21
+ Start-SCOMMaintenanceMode -Instance $Instance -EndTime $EndT ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Microsoft.Syste...anceModeCommand:StartSCMaintenanceModeCommand) [Start-SCOMMaintenance
Mode], ArgumentOutOfRangeException
+ FullyQualifiedErrorId : ExecutionError,Microsoft.SystemCenter.OperationsManagerV10.Commands.StartSCMaintenanceModeCommand
I've tried to look at Start-SCOMMaintenanceMode help online, but I don't see that "startTime" is a parameter. So what is this error message talking about? What am I missing?Thanks for your help. I didn't see your response until just now, but I have been playing around with this all since my last response. I got it to work. I wish I could pinpoint what exactly I changed to get it to work, but I
feel like I've been changing so much stuff that I'm not sure any more.
Just in case anyone finds it useful, here is the code.
[CmdletBinding(SupportsShouldProcess=$true)]
param
[Parameter(Mandatory=$True,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='What is the server you want to put in Maintenance Mode?')]
[Alias("Server")]
[string[]]$ServerName,
[Parameter(Mandatory=$True,
ValueFromPipeline=$false,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Specifies the time the maintenance will end. The minimum amount of time a resource can be in maintenance mode is 5 minutes. This is a required parameter. Format is 1/29/2014 8:59:26 AM')]
[Datetime]$end,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='PlannedOther, UnplannedOther, PlannedHardwareMaintenance, UnplannedHardwareMaintenance, PlannedHardwareInstallation, UnplannedHardwareInstallation, PlannedOperatingSystemReconfiguration, UnplannedOperatingSystemReconfiguration, PlannedApplicationMaintenance, ApplicationInstallation, ApplicationUnresponsive, ApplicationUnstable, SecurityIssue, LossOfNetworkConnectivity')]
[string]$Reason,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Allows you to type a comment about the maintenance activity.')]
[string]$Comment,
[switch]$EventLog
set-strictmode -version latest
#$start=Get-Date
#$currentlog = $start.ToString()
Write-Verbose "Starting $($myinvocation.mycommand)"
Write-Verbose "Ready to put ServerName $ServerName in Maintenance Mode"
Function Start-SCOMMaintenanceModeForServer
[CmdletBinding(SupportsShouldProcess=$true)]
param
[Parameter(Mandatory=$True,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='What is the server you want to put in Maintenance Mode?')]
[Alias("Server")]
[string[]]$ServerName,
[Parameter(Mandatory=$True,
ValueFromPipeline=$false,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Specifies the time the maintenance will end. The minimum amount of time a resource can be in maintenance mode is 5 minutes. This is a required parameter. Format is 1/29/2014 8:59:26 AM')]
[Datetime]$end,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='PlannedOther, UnplannedOther, PlannedHardwareMaintenance, UnplannedHardwareMaintenance, PlannedHardwareInstallation, UnplannedHardwareInstallation, PlannedOperatingSystemReconfiguration, UnplannedOperatingSystemReconfiguration, PlannedApplicationMaintenance, ApplicationInstallation, ApplicationUnresponsive, ApplicationUnstable, SecurityIssue, LossOfNetworkConnectivity')]
[string]$Reason,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Allows you to type a comment about the maintenance activity.')]
[string]$Comment,
[switch]$EventLog
Begin
Write-Verbose "Starting Function Start-SCOMMaintenanceModeForServer"
#Check for minumum Maintenance mode period of 5 mins.
$start = Get-Date
$5MinFromNowTime = $start.AddMinutes(5)
#$end = [datetime]$end
$end = $end.AddSeconds(5)
if($end -lt $5MinFromNowTime)
Write-Error "The time span for the maintenance mode should be at least 5 minutes." -ErrorAction Stop
Write-Verbose "Following server will be put in Maintenance Mode: $ServerName"
$MSs = Get-SCOMManagementServer
} #End Begin
Process
Write-Verbose "Checking if server $ServerName is a Management Server"
#Write-Verbose ($MSs | Select DisplayName)
if(($MSs | Select DisplayName) -eq $ServerName)
Write-Verbose "We don't want to put a Management Server in Maintenance Mode. Skipping"
else
Write-Verbose "Let's put server $ServerName in Maintenance Mode"
$Instance = Get-SCOMClassInstance -Name $ServerName
if ($PSCmdlet.ShouldProcess("Putting $ServerName in Maintenance Mode until $($end).") )
Write-Verbose ("Start-SCOMMaintenanceMode -Instance " + $Instance + " -EndTime " + $end + " -Reason " + $Reason + " -Comment " + $Comment)
Start-SCOMMaintenanceMode -Instance $Instance -end $end -Reason $Reason -Comment $Comment
}#End of whatif
}#End of else
if ($PSBoundParameters['EventLog'])
write-eventlog -LogName "Operations Manager" -Source "OpsMgr SDK Service" -EventID 999 -message "The following Objects are put into in Maintenance Mode until $($end) : $($ServerName)"
}#End if
} #End Process
End
Write-Verbose "Finished Function Start-SCOMMaintenanceModeForServer Function"
#Main
try
if ($PSBoundParameters['EventLog'])
write-eventlog -LogName "Operations Manager" -Source "OpsMgr SDK Service" -EventID 998 -message "The $($myinvocation.mycommand) is used to put Objects in Maintenance Mode"
Write-Verbose "Checking if OperationsManager Module is loaded"
#Check if OperationsManager Module is loaded.
if(!(Get-Module OperationsManager))
Write-Verbose "Importing OperationsManager Module"
Import-Module OperationsManager -ErrorAction Stop
Write-Verbose "Checking for OM2012 environment"
#Check if OM2012 is being used.
if(!(Get-Module OperationsManager).Description -eq "Operations Manager OperationsManagerV10 Module")
Write-Error "This script is only for OM2012"
#Call Function
if ($PSBoundParameters['EventLog'])
Start-SCOMMaintenanceModeForServer -ServerName $ServerName -end $end -Reason $Reason -Comment $Comment -EventLog
else
Start-SCOMMaintenanceModeForServer -ServerName $ServerName -end $end -Reason $Reason -Comment $Comment
} #End Try
catch [System.IO.FileNotFoundException]
"OperationsManager Module not found"
$_.Exception.Message
catch
Write-Warning "Oops something went wrong"
$_.Exception.Message
$end=Get-Date
Write-Debug ("Total processing time {0}" -f ($end-$start).ToString())
Write-Verbose "Ending $($myinvocation.mycommand)"
There is one remaining problem with this script. It does not correctly check to see if something is a management server. We have two management servers. These are the applicable lines, which I still haven't gotten to work yet. First, this retrieves
the list of my Management servers:
$MSs=Get-SCOMManagementServer
Next, these lines are supposed to check if the server I specified is a management server:
if(($MSs | Select DisplayName) -eq $ServerName)
Write-Verbose "We don't want to put a Management Server in Maintenance Mode. Skipping"
Thanks to the Intellisense pop-up deal, I can see that $MSs does get my two management servers. And I can clearly see that there is a DisplayName column. And I can also see that the $ServerName does match what I put in my command line. But it doesn't
seem to catch them if they are actually equal to each other. I don't know if it's because there's two Management Servers, and it doesn't know how to compare like that? Any idea? Is there some sort of loop I need to write so that it compares is to the DisplayName
for EACH Management Server it finds? Any help would be greatly appreciated. -
Another SCOM Maintenance Mode query/advice...
Hi,
Just looking some advice on setting SCOM Maintenance Mode (using SCOM/SCO 2012R2)...
I want to be able to set a server entirely into MaintMode, ie similar to choosing "Selected object AND ALL their contained objects" from SCOM console.
I had asked similar question back in SCOM 2007/Opalis days, but the solution then (placing server and health server watchers separately into maintenance as per Anders blog http://contoso.se/blog/?p=2164 I'm not sure is appropriate now as I believe MaintMode
is handled differently in 2012.
I have seen some pretty complex solutions where using custom built DBs to hold MaintMode status etc. Was hoping theres a neater/simpler soultion using the Orchestrator Activities these days.
If not possible using Native Orchestrator then the fallback would be to try use powershell commandlet. Looking at the Commandlet Examples if I used the following example solution, will that effectively put the server object (and all contained objects
into maintenance which is what I'm trying to achieve.
Windows PowerShell
PS C:\> $Instance = Get-SCOMClassInstance -Name "Server01.Contoso.com"
PS C:\> $Time = ((Get-Date).AddMinutes(10))
PS C:\> Start-SCOMMaintenanceMode -Instance $Instance -EndTime $Time -Comment "Applyin
Any advice to this recurring pain point of SCOM much appreciated.
PS. Not sure if this post is better placed here or in SCOM/Powershell forum so can move if necessary...Hi Michael,
thanks for your reply confirming the powershell command will work.
I have actually just tried using the native Start Maintenance Mode Activity which actually seems to do as required - if the monitor selected is the relevant <servername> : Microsoft.Windows.Computer: <servername> object then it seems to put the
entire server into maintenance. I tested against a server which happened to also host SQL role, so when I placed in Maint via the runbook I then stopped the SQL service and no alerts generated from SQL MP and I could see the spanner Icon against
the server in relevant SQL node views aswell.
I had though maybe that only windows MP stuff might be supressed - so again when I came across all the very complex solutions to apply Maint mode properly I wasnt sure if it was still relevant in 2012 (even though some of those solutions indicated for use
on SCOM/SCO 2012?)
Anyway if the simple solution work - as it appears to do so, then I'll run with that - unless someone can tell me why not?...
Cheers -
How to schedule Maintenance Mode in SCOM 2012?
Hi
How do I schedule Maintenance Mode in SCOM 2012? Do we have any tool for 2012 like we had with 2007?
Regards,
Akhilesh
Thanks, AkhileshYep - to add a calendar takes some extra steps:
E.g.
1) Create a database which includes a table to store information such as:
- target for maintenance mode
- scheduled time for maintenance mode
- Comments
- Duration
- Reason
2) The Service Request fires off an Orchestrator runbook that stores this information in the database
3) Another Runbook that runs frequently that checks the database to see if it should kick off maintenance mode.
It isn't any easy solution for maintenance mode. It works better for more simplistic scheduling e.g. we do implement this kind of logic for environment refreshes and backups where we use the SM Portal and Orchestrator to log a date and then have another
runbook that runs at 2am every day to check if it should execute a backup \ refresh.
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
Maybe you are looking for
-
Hi. I've just moved from Gigastudio/cubase/pc to Logic/Mac and I'm having trouble using new ESX24 samples I'm installing onto the ESX24 sampler. The notes are not mapped out properly across the keyboard - it only seems to use/see two of the samples w
-
I had this problem originally about 3-4 months back and buying another cable corrected it. that costed me $15 right there. I seem to be having the same issue again 3-4 months more down the road. I swapped to an off brand one i had from a transaction
-
How to use iostream.h on C on Xcode?
First of all I must say I'm a NOOB both in programming C as in Xcode. I started college this month and all the basic programming lessons are in C and using iostream.h file. And averybody uses PC/Windows there. I already had Xcode installed and after
-
Can we optimize the query : It is taking a lot of time
the following query is taking a lot of time ... Can anyone suggest to make it run faster ??? table B has 12 million records table a has 10000 records CREATE TABLE less_time PARALLEL NOLOGGING AS SELECT a.user_id,a.mp_id, COUNT(pro
-
Hi I have a webpage that I want to display on an iPad without the user having to zoom out when they first load it. It's a 1920x1080 page -- that is, it has a jpeg background image 1920x1080 and it has text elements overlayed in various places on it.