Maintenance mode message on boot (svc.configd signalled: BUS)

Has anyone seen this kind of message before at boot?
(See /lib/svc/share/README for more information.)
svc.configd signalled: BUS
My server was unresponsive and this may be the cause.
Thanks for the help,
-Todd

Thanks for your attention.
In the above logs, higher resolutions seems to be detected on both screens, hence my surprise :
[ 391.631] (II) intel(0): Printing probed modes for output LVDS1
[ 391.631] (II) intel(0): Modeline "1600x900"x60.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
[ 391.897] (II) intel(0): Printing probed modes for output HDMI1
[ 391.897] (II) intel(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP)
If it can help here is also my current xrandr output (after having called it manually to use the preferred resolution of each screen)
itanguy ~ $ xrandr
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1600x900 60.0*+ 40.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm
1680x1050 59.9*+
1280x1024 75.0 60.0
1152x864 75.0
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
If needed, I may reboot and provide xrandr output after boot (it will be 1024x768), or could other logs help you ? Please ask...

Similar Messages

HELP: WLC AP-SSO not working (standby unity in maintenance mode)

I have two WLC version 7.3.101.0 with the standby unit having HA-SKU. I have tested the AP-SSO functionality without any problem in lab with direct connection on RP port between two WLC. Once I brought them into data centre in separate location (latency is less than 10ms between the two DC), the standby unity always went into maintenance mode. The booting process on standby unit went to maintenance mode as shown below:
Management Gateway and Peer Redundancy Management interface are not reachable.
Entering maintenance mode...
I have checked on the core switches at 2 data centre that the two WLC RP ports are connected to same VLAN and it is spanned across MAN link (10GB and less than 10ms delay). The spanning tree on those ports are forwarding as well.
I have rebooted the second unit but no luck.
The interface between two DC is using MTU 9216 which I do not think would cause this issue.
Anyone has come across same or similar issue with me or know the solution? If you do, plz enlighten me.
Thanks

Thanks Leo and Scott for your feedback. I notice there are two newer software for WLC version 7.3.102.0 and 7.4.100.0.
Both of them seem to have many open caveats. In my wireless environment, I also use ISE, MSE and Prime Infrastructure and unfortunately WLC 7.4 does not support prime solution and MSE yet according to below compatibility matrix.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
I think I only have choice to do minor upgrade to 7.3.102.0 at this moment (please correct me if I am wrong). This software was published on 30th Jan 2013 so I wonder if someone else has tried this and managed to get WLC AP-SSO setup working flawlessly where 2nd WLC unit is at different location?
Appreciate for more info and advise.

Machine booting up to maintenance mode only

Hi guys,
I have a problem with one of my Solaris 10 Servers. The issue is it is always going to maintenance-mode.
I'm getting the follwoing message while botting up.
+\+
WARNING: The following files in / differ from the boot archive:
The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
+"svcadm clear system/boot-archive"+
When i logged in failsafe mode, the OS partition is mounted as /a .
Then i edited vfstab, and then did bootadm as follows
bootadm update-archive -R /
But after restaring the machine goes to maintenance mode.
Any clue to get rid of it ?
Thanks in advance..

Hi Hitesh,
I tried it but the problem is if i logged in on maintenance mode, i can't execute the svcadm
(not only this, any of the commands like vi, ls etc)
What i found is the /usr is not mouting properly in maintenance mode.
hence it is not able to go to sbin and hence all the executables.
and on failsafe mode, i can't clear it also.
# svcadm clear system/boot-archive
svcadm: Instance "svc:/system/boot-archive:default" is not in a maintenance or degraded state.
jj

Booting to maintenance mode

Hi
still being new to solaris10 i,m having probs, i had the same prob b4 solaris not booting up so reinstalled again, booted ok, tried it a couple of times went to on to day wont boot up hav followed wot screen says wih tryin different ways to boot cant get any further than maintenance mode hav got into failsafe but cannot do anything, tried running "svcadm clear system/boot-archive etc

Hi Hitesh,
I tried it but the problem is if i logged in on maintenance mode, i can't execute the svcadm
(not only this, any of the commands like vi, ls etc)
What i found is the /usr is not mouting properly in maintenance mode.
hence it is not able to go to sbin and hence all the executables.
and on failsafe mode, i can't clear it also.
# svcadm clear system/boot-archive
svcadm: Instance "svc:/system/boot-archive:default" is not in a maintenance or degraded state.
jj

Laptop mode -- where to find error messages on boot

Hi guys,
I get some error messages when booting. I have the time to read that they are related to laptop-mode, but they quickly disappear.
I have activated the ENABLE_LAPTOP_MODE_TOOLS in my laptop-mode.conf file, but I can't find the error messages in /var/log :
/var/log » ll nico@cotier
total 2152
-rw-r--r-- 1 root users 24082 20 mars 11:30 Xorg.0.log
-rw-r--r-- 1 root users 24084 20 mars 10:35 Xorg.0.log.old
-rw-r--r-- 1 root users 28050 1 juin 2013 Xorg.1.log
-rw-r--r-- 1 root users 27492 1 juin 2013 Xorg.1.log.old
-rw-r--r-- 1 root bumblebee 13679 1 juin 2013 Xorg.8.log
-rw------- 1 root utmp 18816 20 mars 10:18 btmp
-rw------- 1 root root 32032 20 mars 11:29 faillog
drwxr-xr-x 2 root root 4096 16 juin 2013 httpd
drwxr-sr-x+ 3 root systemd-journal 4096 1 juin 2013 journal
-rw-r--r-- 1 root root 292292 20 mars 11:29 lastlog
drwxr-xr-x 2 root root 4096 14 mars 2013 old
-rw-r--r-- 1 root root 159892 19 mars 14:55 pacman.log
-rw-r--r-- 1 root root 77572 5 oct. 00:47 pm-powersave.log
-rw-r--r-- 1 root root 3586 1 juin 2013 slim.log
drwxr-xr-x 2 root root 4096 9 mars 2013 speech-dispatcher
-rw-rw-r-- 1 root utmp 1745280 20 mars 11:45 wtmp
Do you know where they might be?
Thanks!

grep all these logs and systemd's journal.
If you have 'quiet' on the kernel line of your bootloader, remove it.
Last edited by karol (2014-03-20 11:52:42)

Can't boot up the 640 G1 Laptop. ME Unlock is forbidden in Production Mode message comes up

Can't boot up the 640 G1 Laptop. "ME Unlock is forbidden in Production Mode" message comes up

Hi ,
I have brought your issue to the attention of an appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message after the weekend from an identified HP contact. Additionally, keep in mind not to publically post ( serial numbers and case details)
If you are unfamiliar with how the Forum's private message capability works, you can learn about that here.
Regards,
George

Requesting System Maintenance Mode

I just installed Solaris 10 on a SunFire v100 and patched the os. I added a second drive and mirrored it. Now I get this message 2 out of 3 times when I reboot the server.....
LOM event: +36d+22h57m55s host reset
Sun Fire V100 (UltraSPARC-IIe 548MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #57166297.
Ethernet address 0:3:ba:68:49:d9, Host ID: 836849d9.
Executing last command: boot
Boot device: rootdisk File and args:
SunOS Release 5.10 Version Generic_118822-27 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: gandalf
Jan 31 17:41:02 svc.startd[7]: svc:/system/boot-archive:default: Method "/lib/sv<br />
c/method/boot-archive" failed with exit status 1.
Jan 31 17:41:02 svc.startd[7]: svc:/system/boot-archive:default: Method "/lib/sv<br />
c/method/boot-archive" failed with exit status 1.
Jan 31 17:41:02 svc.startd[7]: svc:/system/boot-archive:default: Method "/lib/sv<br />
c/method/boot-archive" failed with exit status 1.
[ system/boot-archive:default failed (see 'svcs -x' for details) ]
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
Any clue on what I should do?
Thanks!
Chris Edwards

Hi,
Can you please check the below note
Solaris11 cannot boot and goes into maintenance ( svc:/system/early-manifest-import:default exited with status 1 ) (Doc ID 1526559.1)
It has the solution workaround. Kindly let us know in case issue is not fixed
Thanks,
Krishna

Unable to enter maintenance mode - dtrt1000

Over the last few weeks my box is almost useless. With frequency it only part records, freezes requiring rebooting, momintary screen blanks, and is generally a pain in the rear. I've tried to get into maintenance mode to try and reset it, but following the guide from Youview it doesn't work, and the box just starts as normal.
My understanding is that you (1) Switch the box off from the back (2) Switch it back on after 30secs (3) Press the power button and immediately hold of the -vol button until the splash screen appears...Then you can access the menu.
I've tried holding the holiding the -vol button before the power button, holding it immediately after power button, holding it until the nearly ready screen, in low and high eco modes etc but get the same result, it just goes straight into normal programes???

1 Start with the YouView box powered off from the switch on the REAR panel power button
2. Power back on the YouView box using the REAR panel power button
3. When the FRONT power button is illuminated with an orange circle, press the FRONT panel power button firmly once and it will turn blue
4. Immediately press and hold the "VOL-" button which can be found on the right of the FRONT panel the first silver button.
5. A message saying "Enter Maintenance Mode Y/N (Y: POWER)" appears on the TV screen
So if I understand correctly your experience is that steps 1, 2 & 3 occur but when doing step 4 the message step 5 (does not occur ) and your box boots as normal.
My own (historic ) experience is that the timing of stages 3 and 4 is quite tight - ie the power button turning blue followed immediately by the VOL- button being pressed and held.
Your options if the maintenence mode will not work are to contact BT support and seek their advice or if you are not concerned about the recordings remaining on the box you can do a factory reset from from main Youview menu
https://community.youview.com/youview/topics/top_tip_soft_reset_reboot_power_cycling_maintenance_mod...

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.
Randy

Thanks 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

VDI 3.1 cloning fail if one esx from a cluster is in maintenance mode

hi
i have a vsphere cluster with 2 esx included and ha and drm enabled
if one of the esx is in maintenance mode the cloning job failes but with a misleading error message
INFO: Datastore 'Sun Storage 1' is not available for cloning, it is disconnected or in maintenance mode
i see here 2 bugs
1) the wrong error message cause the datastore is neither disconnected nor in maintenance mode
2) cloning should still possible if one esx server is not available
br
Andre

Hi login,
It should be possible. You will need to route the output of the counter to a specific RTSI line and then use that line as the sample clock by the MIO board. The function you will want to use to route the counter output to the RTSI bus is the Route Signal.vi in LabVIEW or the Select_Signal() in NI-DAQ function calls. You will want to use constants such as ND_GPCTR[x]_OUTPUT where [x] is the counter number and ND_RTSI_[x] where [x] is the RTSI line number. Your source is the counter output and your signal is the RTSI line of choice.
Similarly, for the MIO card, you will want to route the RTSI line to the AI Scan Start to route to your scan clock. The constant for this should be ND_IN_SCAN_START and it should be the signal value while your RTSI s
hould be the source.
The point is you will need to route the signal for both cards which amounts to 2 calls (or 2 VIs). Anyway, hope that helps. Have a good day.
Ron
Applications Engineering
National Instruments

SUNFIRE V880 in maintenance mode

Hi,
Sunfire V880 server start to maintenance mode and in run level 6.
I have try to boot to solais DVD rfrom ok prompt and cannot boot.
this is imposible to modify in runlevel 6 vfstab or inittab.
wath can i do please help me.
thank you

Hi.
Please describe current state and what you see on terminal
Level init 6 - mean reboot the system. So it can not be stable state.
What error messages you got when try boot from DVD ? What Solaris version you try boot ?
What Solaris version was installed on server ?
Regards.

FWSM maintenance mode - vlan 1

Hi,
A client has had their FWSM fail, when you try to start the module the switch eventually disables the power to that slot (%C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Module Failed SCP dnld)). I have turned off diagnostics with 'no diagnostic boot level' and then use 'boot device module 4 cf:1' to bring the FWSM up into maintenance mode. I can then session up from the switch and log in to the FWSM as root.
After inputting all the necessary IP info I can't ping anything on vlan 1 as I would expect, I have set the FWSM as 192.168.1.2 and a FTP/TFTP server as 192.168.1.1
I have removed the firewall vlan groups and tried to put them back with just vlan 1 but this isn't accepted (the reasons are covered in other posts on the forum). What am I doing wrong as the instruction say that vlan 1 is the only vlan that is accessable whilst the FWSM is in maintenance mode.
I can create an int vlan 1 in the switch and ping my ftp server so know that the switchport is set up correctly, I can also see that Po308 is formed and when the module boots I can see the Gi4/xx interfaces come up (FWSM is in slot 4).
Any ideas of what to try next?
............and they aren't covered by maintenance agreements
FWSM
Maintenance image version: 2.1(4)
[email protected]#show images
Device name             Partition#              Image name
Compact flash(cf)       4                       c6svc-fwm-k9.3-1-4-0.bin
Switch
SWITCH# sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXI7, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Mon 18-Jul-11 05:49 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)
Regards
Mel

Recently i met the same problem.
When installing FWSM board on the Catalyst 6509 there is not communication access via vlan1 in the maintenance partition.
Moreover, the FWSM works properly in the aplication partition(cf:4).
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXH8, RELEASE SOFTWARE (fc1)
System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)
Mod Ports Card Type                              Model
1   48 48-port 10/100/1000 RJ45 EtherModule   WS-X6148A-GE-TX
4    6 Firewall Module                        WS-SVC-FWM-1
5    2 Supervisor Engine 720 (Active)         WS-SUP720-3BXL
8    5 Communication Media Module             WS-SVC-CMM
Mod MAC addresses                       Hw    Fw           Sw           Status
1 001b.d41a.8360 to 001b.d41a.838f   1.5   8.4(1)       8.7(0.22)BUB Ok
4 0003.fead.962e to 0003.fead.9635   3.0   7.2(1)       4.1(14)      Ok
5 0017.9444.c3ec to 0017.9444.c3ef   5.4   8.5(2)       12.2(33)SXH8 Ok
8 0017.0ee2.13cc to 0017.0ee2.13d5   2.8   12.4(25c),   12.4(25c),   Ok
FWSM versions
FWSM Firewall Version 3.2(20)
Device Manager Version 5.0(3)F
Not possible to verify the switch is in the service.
I guess the reason is likely next.
FWSM supports only untagged packets on the vlan1. By default catalyst 6500 not tagged native vlan1.
In my case globally enabled tagging in the native vlan.
#sh vlan dot1q tag native
dot1q native vlan tagging is enabled globally
sh vlan dot1q tag native
dot1q native vlan tagging is enabled globally
Per Port Native Vlan Tagging State:
Port    Operational          Native VLAN
           Mode               Tagging State
Gi1/2   trunk                 enabled
Gi1/8   trunk                 enabled
Gi1/13 trunk                 enabled
Gi1/14 trunk                 enabled
Gi1/17 trunk                 enabled
Gi1/18 trunk                 enabled
Gi1/21 trunk                 enabled
Gi1/27 trunk                 enabled
Gi1/30 trunk                 enabled
Gi1/32 trunk                 enabled
Gi1/38 trunk                 enabled
Gi1/42 trunk                 enabled
Gi1/43 trunk                 enabled
Gi1/44 trunk                 enabled
Gi1/46 trunk                 enabled
Gi5/2   trunk                 enabled
Po2     trunk                 enabled
Po308   trunk                 enabled

Maintenance Mode Switch for APEX

Is there any way that I can throw an switch in APEX and have it allow users who are currently logged in to finish their sessions (maybe displaying an alert message at the top of their pages asking them to finish what they are doing quickly and logout) but display a message denying new users the ability to login and use APEX. What I am after is a way to gracefully clear users off of my app server so I can take it down without giving a grand maul das boot to active users. Kind of the "The store is now closing, please take your final purchases to the registers at this time." type of announcement. Lock the front doors but let people who are already inside finish their business type of result. If this does not exist, it would be a nice feature to have at the internal workspace control level.

Hi,
A Windows Schedule task,
http://technet.microsoft.com/en-us/library/cc748993.aspx
Please read this one:
Management Pack for the SCOM 2012 Maintenance Mode Scheduler
http://blog.tyang.org/2014/05/22/management-pack-scom-2012-maintenance-mode-scheduler/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

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.
Rahul

1. 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

5508-HA standby in Maintenance mode

My standby controller is in maintenance mode. Other post say to simply reboot the standby but I'm worried about doing this during business hours. Say I did reboot it during business hours, would it affect the active controller? All redundancy links are connected.
(Cisco Controller) >show redundancy sum
Redundancy Mode = SSO ENABLED
Local State = MAINTENANCE
Peer State = UNKNOWN - Communication Down
Unit = Secondary - HA SKU
Unit ID = 00:06:F6:DC:17:00
Redundancy State = Non Redundant
Mobility MAC = 68:EF:BD:8E:61:E0
Maintenance Mode = Enabled
Maintenance cause= Negotiation Timeout

No it won't affect the active controller:
While booting, the WLCs will negotiate the HA role as per the configuration done. Once the role is determined, the configuration is synced from the Active WLC to the Standby WLC via the Redundant Port. Initially WLC is configured, as Secondary will report XML mismatch and will download the configuration from Active and reboot again. During the next reboot after role determination, it will validate the configuration again, report no XML mismatch, and process further in order to establish itself as the Standby WLC
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.pdf
https://supportforums.cisco.com/discussion/11758901/ask-expert-high-availability-wireless-lan-controller-wlc

Maintenance mode message on boot (svc.configd signalled: BUS)

Similar Messages

Maybe you are looking for