Powersave not restarting network properly after suspend

My laptop uses ethernet hardware supported by the sky2 module, which must be unloaded before suspend. Network has to be restarted after the module is reloaded or ethernet stays kaput. So, I edited my /etc/powersave/sleep like this:
## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "nvsound acx100 acx_pci hsfmodem prism54 bcm4400 emu10k1 forcedeth ipw2100 ipw2200 natsemi psmouse rt2400 ehci_hcd ohci_hcd uhci_hcd ehci-hcd usb-ohci usb-uhci snd_ens1370 snd_ens1371 en1370 en1371 via_agp via_rhine i8042 intel_mch_agp rt2500 button speedstep_smi ndiswrapper"
## ServiceRestart: "network,alsa,netfs"
# These modules will be unloaded before entering suspend to disk
# See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="prism54 sky2 ath_pci"
## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "nvsound acx100 acx_pci hsfmodem prism54 bcm4400 emu10k1 forcedeth ipw2100 ipw2200 natsemi psmouse rt2400 ehci_hcd ohci_hcd uhci_hcd ehci-hcd usb-ohci usb-uhci snd_ens1370 snd_ens1371 en1370 en1371 via_agp via_rhine i8042 intel_mch_agp rt2500 button speedstep_smi ndiswrapper"
## ServiceRestart: "network,alsa,netfs"
# These modules will be unloaded before entering the corresponding
# sleep state. See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="prism54 sky2 ath_pci"
## Path: System/Powermanagement/Powersave/Sleep_Modes
### Type: string
## Default: "nvsound acx100 acx_pci hsfmodem prism54 bcm4400 emu10k1 forcedeth ipw2100 ipw2200 natsemi psmouse rt2400 ehci_hcd ohci_hcd uhci_hcd ehci-hcd usb-ohci usb-uhci snd_ens1370 snd_ens1371 en1370 en1371 via_agp via_rhine i8042 intel_mch_agp rt2500 button speedstep_smi ndiswrapper"
## ServiceRestart: "network,alsa,netfs"
# These modules will be unloaded before entering the corresponding
# sleep state. See README.unload-modules for more information.
# "NONE" means don't unload any modules.
UNLOAD_MODULES_BEFORE_STANDBY="prism54 sky2 ath_pci"
## Path: System/Powermanagement/Powersave/Sleep_Modes
## Type: string
## Default: "slmodemd irda"
# All services that have to be stopped before entering a sleep mode
# and restarted after the machine resumes.
# If you notice problems of some services that may be related to
# suspend/standby, restarting the service may solve the problem.
# The names to enter here are simply the filenames of the init scripts
# in /etc/init.d. The services are stopped in the order entered here.
# They are restarted after resume in the reverse order.
# Entering "NONE" disables restarting of services ("" means default).
SUSPEND2DISK_RESTART_SERVICES="network"
SUSPEND2RAM_RESTART_SERVICES="network"
STANDBY_RESTART_SERVICES="network"
Problem is, powersaved doesn't restart the network like it ought to. The log gives me this:
suspend2ram initiated: 2007-06-05 07:05:46 PM
Debug info follows here, please include in your bug reports. Thanks.
Loaded modules:
Module Size Used by
sky2 37896 0
rtc_sysfs 3840 0
rtc_proc 3844 0
snd_seq_oss 29056 0
snd_seq_midi_event 6528 1 snd_seq_oss
snd_seq 46800 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 6796 2 snd_seq_oss,snd_seq
joydev 8384 0
usbhid 36256 0
hid 24448 1 usbhid
ff_memless 5256 1 usbhid
snd_pcm_oss 38816 0
rtc_dev 6792 0
snd_mixer_oss 14336 1 snd_pcm_oss
pcmcia 31404 0
rtc_cmos 7188 0
i2c_i801 7952 0
i2c_core 17664 1 i2c_i801
rtc_core 7684 4 rtc_sysfs,rtc_proc,rtc_dev,rtc_cmos
rtc_lib 3456 2 rtc_sysfs,rtc_core
tifm_7xx1 6912 0
tifm_core 6784 1 tifm_7xx1
ath_pci 88224 0
wlan 188868 1 ath_pci
pcspkr 2944 0
psmouse 35080 0
serio_raw 5636 0
ath_hal 190032 1 ath_pci
snd_hda_intel 254104 1
snd_pcm 68484 2 snd_pcm_oss,snd_hda_intel
snd_timer 19076 2 snd_seq,snd_pcm
snd 44388 10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer
soundcore 6496 1 snd
yenta_socket 23180 1
rsrc_nonstatic 11136 1 yenta_socket
pcmcia_core 32920 3 pcmcia,yenta_socket,rsrc_nonstatic
sg 26780 0
snd_page_alloc 7816 2 snd_hda_intel,snd_pcm
ehci_hcd 31116 0
uhci_hcd 22032 0
tsdev 6464 0
evdev 8192 6
thermal 11656 0
processor 24788 1 thermal
fan 3972 0
button 6288 0
battery 8580 0
ac 4100 0
i915 21376 2
drm 70548 3 i915
intel_agp 21404 1
agpgart 27608 3 drm,intel_agp
usbcore 111752 4 usbhid,ehci_hcd,uhci_hcd
ext3 118536 2
jbd 54952 1 ext3
mbcache 6916 1 ext3
sr_mod 14372 0
cdrom 34080 1 sr_mod
sd_mod 17668 3
ata_generic 5636 0
ata_piix 11780 2
libata 102164 2 ata_generic,ata_piix
Memory info:
total used free shared buffers cached
Mem: 506356 370360 135996 0 7444 87180
-/+ buffers/cache: 275736 230620
Swap: 0 0 0
/proc/cmdline: root=/dev/sda1 ro idle=halt acpi_sleep=s3_mode
========we are going to sleep, preparing.========
== checking runlevel ==
no shutdown/reboot in progress, good.
== Unmounting FAT/NTFS filesystems: ==
none found in /etc/mtab
== FAT/NTFS filesystems unmounted ==
Stopping services: ('network' configured)
none running.
ejecting PCMCIA cards...
Unloading modules: ('prism54 sky2' configured)
checking prism54
checking sky2
# trying to unload: sky2
unloaded: sky2
prepare_sleep finished for suspend2ram
/usr/sbin/s2ram not found, falling back to echo.
==== finished, return code 0 ====
========we are back from suspend, cleaning up.========
== restore_after_sleep: restart and reload everything ==
Resuming:
switched back to console: ' 7'
Reloading modules:
sky2
inserting PCMCIA cards...
Restarting services:
Remounting filesystems:
not necessary.
======================================
restore_after_suspend_to_ram: finished
Apparently network is considered already accounted for, but it isn't. I have to restart the script manually. What's up with this?

Umm... OP? Log doesn't say that network fails, but appears to indicate that powersaved does not try to restart it. I'll give it a shot but it looks completely irrelevant.
Edit: Well I'll be damned, it worked. Just a second, I'm going to do a bit more messing around...
Edit again: Hmm, strange, works without the 5-second wait now. Damned if I know what was up with that.
Last edited by Gullible Jones (2007-06-06 01:35:48)

Similar Messages

  • Networked computer will not join network automatically after restart/sleep

    Situation:
    I've got two computers - PowerBook 17" 1,25 GHz, iMac 2,16 GHz 24", both running OS X 10.4.8. They are networked via AirPort Express, firmware v. 6.3, in a WPA protected network. The AirPort distributes ADSL 4 Mbps connection.
    Computers are set as DHCP with manual address (to keep stable LAN address)
    The problem: While the PowerBook always joins the network after restart/sleep automatically, iMac in such a situation never goes online - the airport status in menu bar is on, the network is checked, but it cannot connect or be reached.
    I always have to manually turn airport of from menu bar, then turn it on, then wait about 20 seconds and then manually choose name of my network.
    After this procedure iMac is finally online.
    Settings of the AirPort are:
    AirPort tab
    Wireless Security: WPA2 personal
    Channel: Automatic
    Mode: 802/11 g/b
    Internet tab
    Connecting using: Ethernet
    Configure: Using DHCP
    WAN ethernet port: Automatic
    Network tab
    Distribute IP address unchecked (no difference when checked - tested)
    Any idea how to fix it?
    Thanks in advance!
    PowerBook 1,25 17", iMac 24"   Mac OS X (10.4.8)  

    Thanks a bunch, Duane!
    You pointed me to the exact answer.
    iMac joins the network automatically now, although I had to change original automatic login of an admin user to manual login page, because after automatic login as one of three users, an error message "Network error" appeared quicker than the actual joining the network, that came a few seconds later.
    After manual logging (it probably needed a little more time) it's OK.
    Thanks again and greeting from Czech Republic!
    PowerBook 1,25 17", iMac 24"   Mac OS X (10.4.8)  

  • [SOLVED] Losing network connection after suspend

    Lately I'm having this peculiar problem.  When resuming after suspend (specifically, pm-suspend), I have no network connection.  I first noticed this on March 31st.  The only thing that changed was that I upgraded these packages:
    openssl-1.0.1-2-x86_64.pkg.tar.xz
    xf86-video-ati-6.14.4-2-x86_64.pkg.tar.xz
    lib32-libdrm-2.4.33-1-x86_64.pkg.tar.xz
    libnotify-0.7.5-1-x86_64.pkg.tar.xz
    xz-5.0.3-2-x86_64.pkg.tar.xz
    vim-taglist-45-5-any.pkg.tar.xz
    But I'm pretty sure I would have suspended and resumed successfully at least once after that upgrade.
    Can anyone suggest what I should look at to try to diagnose this?
    Thanks
    Last edited by ibrunton (2012-04-06 11:26:03)

    Same issue here. Looks like dhcpcd crashes during or after running /usr/lib/dhcpcd/dhcpcd-run-hooks on resume from suspend. I'll try downgrading until this is fixed.
    $ uname -s -v -r -m
    Linux 3.2.13-1-ARCH #1 SMP PREEMPT Sat Mar 24 09:10:39 CET 2012 x86_64
    $ pacman -Qi dhcpcd
    Name : dhcpcd
    Version : 5.5.5-1
    URL : http://roy.marples.name/dhcpcd/
    Licenses : BSD
    Groups : base
    Provides : None
    Depends On : glibc sh
    Optional Deps : None
    Required By : networkmanager
    Conflicts With : None
    Replaces : None
    Installed Size : 256.00 KiB
    Packager : Ronald van Haren <[email protected]>
    Architecture : x86_64
    Build Date : Fri Mar 23 17:25:47 2012
    Install Date : Thu Mar 29 23:36:13 2012
    Install Reason : Explicitly installed
    Install Script : No
    Description : RFC2131 compliant DHCP client daemon
    # dhcpcd -d -B eth0
    dhcpcd[1865]: version 5.5.5 starting
    dhcpcd[1865]: eth0: using hwaddr bc:ae:c5:75:36:8e
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
    dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
    dhcpcd[1865]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
    dhcpcd[1865]: eth0: rebinding lease of 192.168.1.100
    dhcpcd[1865]: eth0: sending REQUEST (xid 0x36169f23), next in 3.93 seconds
    dhcpcd[1865]: eth0: acknowledged 192.168.1.100 from 192.168.1.1
    dhcpcd[1865]: eth0: checking for 192.168.1.100
    dhcpcd[1865]: eth0: sending ARP probe (1 of 3), next in 2.00 seconds
    dhcpcd[1865]: eth0: sending ARP probe (2 of 3), next in 1.81 seconds
    dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
    dhcpcd[1865]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
    dhcpcd[1865]: eth0: leased 192.168.1.100 for 3600 seconds
    dhcpcd[1865]: eth0: adding IP address 192.168.1.100/24
    dhcpcd[1865]: eth0: adding route to 192.168.1.0/24
    dhcpcd[1865]: eth0: adding default route via 192.168.1.1
    dhcpcd[1865]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
    dhcpcd[1865]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds
    dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
    dhcpcd[1865]: eth0: sending ARP announce (2 of 2)
    dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
    dhcpcd[1865]: eth0: no IPv6 Routers available
    dhcpcd[1865]: eth0: carrier lost
    dhcpcd[1865]: eth0: deleting default route via 192.168.1.1
    dhcpcd[1865]: eth0: deleting route to 192.168.1.0/24
    dhcpcd[1865]: eth0: deleting IP address 192.168.1.100/24
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
    dhcpcd[1865]: eth0: carrier acquired
    dhcpcd[1865]: eth0: using hwaddr bc:ae:c5:75:36:8e
    dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
    *** glibc detected *** dhcpcd: double free or corruption (fasttop): 0x0000000000ac2860 ***
    ======= Backtrace: =========
    /lib/libc.so.6(+0x78a56)[0x7f9b6a794a56]
    dhcpcd[0x40cdd0]
    dhcpcd[0x40e597]
    dhcpcd[0x4093f0]
    dhcpcd[0x411ba7]
    dhcpcd[0x411563]
    dhcpcd[0x40768f]
    dhcpcd[0x40aa6b]
    dhcpcd[0x4028a8]
    /lib/libc.so.6(__libc_start_main+0xf5)[0x7f9b6a73d455]
    dhcpcd[0x402d1d]
    ======= Memory map: ========
    00400000-00419000 r-xp 00000000 fe:02 4590719 /sbin/dhcpcd
    00619000-0061a000 r--p 00019000 fe:02 4590719 /sbin/dhcpcd
    0061a000-0061b000 rw-p 0001a000 fe:02 4590719 /sbin/dhcpcd
    0061b000-0061c000 rw-p 00000000 00:00 0
    00ac1000-00ae3000 rw-p 00000000 00:00 0 [heap]
    7f9b6a2eb000-7f9b6a300000 r-xp 00000000 fe:02 1063993 /usr/lib/libgcc_s.so.1
    7f9b6a300000-7f9b6a4ff000 ---p 00015000 fe:02 1063993 /usr/lib/libgcc_s.so.1
    7f9b6a4ff000-7f9b6a500000 rw-p 00014000 fe:02 1063993 /usr/lib/libgcc_s.so.1
    7f9b6a500000-7f9b6a517000 r-xp 00000000 fe:02 3014810 /lib/libpthread-2.15.so
    7f9b6a517000-7f9b6a716000 ---p 00017000 fe:02 3014810 /lib/libpthread-2.15.so
    7f9b6a716000-7f9b6a717000 r--p 00016000 fe:02 3014810 /lib/libpthread-2.15.so
    7f9b6a717000-7f9b6a718000 rw-p 00017000 fe:02 3014810 /lib/libpthread-2.15.so
    7f9b6a718000-7f9b6a71c000 rw-p 00000000 00:00 0
    7f9b6a71c000-7f9b6a8b3000 r-xp 00000000 fe:02 3018245 /lib/libc-2.15.so
    7f9b6a8b3000-7f9b6aab3000 ---p 00197000 fe:02 3018245 /lib/libc-2.15.so
    7f9b6aab3000-7f9b6aab7000 r--p 00197000 fe:02 3018245 /lib/libc-2.15.so
    7f9b6aab7000-7f9b6aab9000 rw-p 0019b000 fe:02 3018245 /lib/libc-2.15.so
    7f9b6aab9000-7f9b6aabd000 rw-p 00000000 00:00 0
    7f9b6aabd000-7f9b6aac4000 r-xp 00000000 fe:02 3014856 /lib/librt-2.15.so
    7f9b6aac4000-7f9b6acc3000 ---p 00007000 fe:02 3014856 /lib/librt-2.15.so
    7f9b6acc3000-7f9b6acc4000 r--p 00006000 fe:02 3014856 /lib/librt-2.15.so
    7f9b6acc4000-7f9b6acc5000 rw-p 00007000 fe:02 3014856 /lib/librt-2.15.so
    7f9b6acc5000-7f9b6ace6000 r-xp 00000000 fe:02 3018769 /lib/ld-2.15.so
    7f9b6aea5000-7f9b6aea9000 rw-p 00000000 00:00 0
    7f9b6aee4000-7f9b6aee6000 rw-p 00000000 00:00 0
    7f9b6aee6000-7f9b6aee7000 r--p 00021000 fe:02 3018769 /lib/ld-2.15.so
    7f9b6aee7000-7f9b6aee8000 rw-p 00022000 fe:02 3018769 /lib/ld-2.15.so
    7f9b6aee8000-7f9b6aee9000 rw-p 00000000 00:00 0
    7ffff8b93000-7ffff8bb4000 rw-p 00000000 00:00 0 [stack]
    7ffff8bc9000-7ffff8bca000 r-xp 00000000 00:00 0 [vdso]
    ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

  • Satellite Pro U400 - Lost network connection after suspend

    I have a Toshiba Dynadock. My network is connect directly in dynadock.
    When suspend my Satellite Pro U400 and after restart for continue working I lost my network connection. Then I shutdown my computer and disconnect/connect Dynadock I can continue working.
    What's the problem?
    Version software Dynadock is 2.0

    Hi
    I see you have switched from Vista to XP.
    First of all I recommend updating the BIOS.
    As Im not mistaken you should find a newer BIOS version on the Toshiba European driver page.
    Then you have to update the Win XP to the latest state!
    The XP should be up to date and all service packs, patches and MS fixes should be installed in your notebook.
    Then access the device manager and mark in every USB root hub you have to disable the option called Allow the computer to turn off this device to save power
    You can find this option in properties -> Power management tab

  • Network configuration after suspend/resume

    After a suspend and when I resume, the network configuration of my wifi card is lost (since the module must be unloaded).
    What do I need to setup so that the settings of the wifi card (ip address, default gw) are remembered on suspend and applyed later on resume?

    But the default network config may not be the last one I used, or the prefered one anyway...
    At least I'd like the network to be initialized the same as it was before suspending.

  • IPhone 4 cannot pick up a network properly after iOS 5 upgrade

    After I upgraded to iOS 5, my iPhone 4 cannot pick up a network if it loses it. If I switch the phone to the airplane mode and then back, it finds something but I cannot neither hear anyone when I make a call nor send sms. I cannot properly cancel a call either, the phone app freezes once I press the cancel button.

    iPhone 4S turned out to be a really bad apple..
    I have, as many others, catastrophic reception on my new iPhone 4S. I might add that I also have an iPhone 4 and if I put the same MicroSim in this phone then the reception is flawless.
    The problem is essentially the same as the one that many other experiences, five full bars, and (in my case) Tele2 3G. If someone tries to call me they are immediately sent to voicemail. If I try to make a call it fails, then the bars go down one by one until no service is shown, then the SIMsearches for reception and usually succeeds after about 1 minute the bars appear again. Sometimes I then can make a call but nine times out of tenthe procedure will just be repeated again.
    I can of course manually get my bars back again via either reboot or by taking out and putting in the SIM again or by activating and then deactivating flight mode, this does not mean that I get actual reception, I just get the bars and operator name back and the phone seems to have reception. That is until I try to make a new call...
    One can't turn off 3G in new iOS5, however, one can select operator manually. Carrier settings in iOS5 defautls to "Auto". If I turn off auto and select Tele2's 2G network nothing happens. I can turn off the "auto" but it is just says "Searching...". If I go back to settings and then back again the carrier settings are in "Auto" mode again.
    I have made several re-installations, both from backup and as a new phone, turned on and off the PIN code, deactivated and activated Location services, made hard resets, etc. Even after the latest beta, which was released developers today, was installed and all procedures were done all over again with this OS the problem persists. It is simply impossible to either make or receive calls with my new iPhone 4S. It can do lots of fancy stuff but as a phone it is completely useless and I am compelled to to go back to using my iPhone 4 for now.
    You would think that Apple would ensure that at least the telephone part in both hardware and software are operating properly before releasing them to consumers. It's called "iPhone" - not iPod, iPhone, iGame...iPhone is primarily a phone and customers buying it would at the very least require it to be able to make and recieve calls or maybe it's asking too much?
    What is also very strange is that even if a lot of consumers complain about the above bug, not only in Sweden but all over the world, Apple does not mention this anywhere. Not on their support pages, not in their developer community, not to their dealers who certainly had a lot of support calls from unhappy customers who believe that it is an operator error.
    Incredibly bad service by Apple to release a phone that can not be used as a phone and even worse to not quickly recognize this error and publish what's causing the error, that they're working on resolving it, and when it will be resolved.
    I work myself as telephony manager at a company that uses just the iPhone and there are now quite a few new unhappy iPhone 4S, and where I take a lot of support concerning these bugs and have to get them temporary solutions until the bugs are fixed.
    I use to commend both Apple and their products, but my conviction on Apple's excellence has been significantly tarnished. This is BAD Apple, hope you get your acts together a.s.a.p. cause both your phone and your service really ***** in this case.
    Only way to get attention is to flood apple with info on this matter: fill in form at: http://www.apple.com/feedback/iphone.html and let them know..

  • Nodemanager does not restart managed server after Linux OS reboot

    Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
    I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
    Things I've tried:
    + When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
    + The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
    + A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
    Things I'm curious about:
    + Is there some way to see in what state the nodemanager believes the managed server to be?
    + Is there some value in some doc somewhere that might say the server should not be restarted?
    + Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
    Thanks,
    Kevin
    ListenPort=5556
    ListenBacklog=50
    SecureListener=true
    AuthenticationEnabled=true
    NativeVersionEnabled=false
    CrashRecoveryEnabled=true
    JavaHome=/appl/java/jre
    StartScriptEnabled=false
    StopScriptEnabled=false
    StartScriptName=startWebLogic.sh
    StopScriptName=
    LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
    LogLevel=INFO
    LogLimit=0
    LogCount=1

    can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
    Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
    To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
    CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
    NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
    Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
    From Official documentation:
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
    If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    */

  • Safari 5.1.5 not loading pages properly after Java install

    Safari kept telling me I need to install a java runtime, so I finally let it, and now certain pages (like accuweather.com)  take forever to load unless I turn off Java in preferences. The page background will appear but the "loading whatever # of #" hangs on the last number and just sits there until the page finally appears. Has anyone else had this problem, and if so, how can it be fixed?

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. The instructions provided by Apple are as follows:
    Be sure your Mac is shut down.
    Press the power button.
    Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem(s)?
    After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Losing (closed) wifi network informations after suspend/resume.

    I get some trouble with MacOS X airport support and suspend/resume on my WIFI network (non airport access point based : I have a linksys wifi/modem/router).
    For security reason my network is closed (no ESSID diffusion). Each time my computer (MacBookPro3,1 - Mac OS X 10.5.1 up-to-date) resume from suspend I am no more connected, and worse the system do not use anymore the information I registered in the network settings apps (ESSID, WEP key) : the network is no more visible, and even if the network is remembered in the list of previously visited network, I am forced to retype everything (ESSID, WEP key) to be able to be connected again.
    When I change my network setup to get an open one (with ESSID diffusion) then it works : I can suspend the computer, resume it an I am connected again without doing anything.
    This is very annoying, since I am not the main user of the computer (main one do not understand anything about network settings) and that I need my network to be closed (no ESSID diffusion).
    With other 4 others different computers (PowerBook Titanium using Max OS X 10.4 / PowerBook Aluminium using Mac OS X 10.3 or 10.4 / MacBookPro using Linux / Dell Latitude using Linux) everything work as expected.
    Any ideas where I can find information on how to fix this (stupid) behavior ?
    BTW, I tested the following with my base configured for 802.11b, 802.11g and automatic detection.

    I am not offering a fix other than to say don't use a closed network.
    I asy this because having a closed network does not offer any network security. A hacker can easily see your network using tools that anyone can download from the internet. Having a closed network can interfere with the efficiency of all wifi network in your area. As your neighbours may be unaware of your network and start broadcasting on the same channel as you. Then you would both have issues.
    WEP encrypton offers no real security either as this too can be cracked sometimes in minutes using tools that anyone can download from the internet.
    The only network security you should consider using is WPA/WPA2.

  • Can not setup network connection after netctl 1.10 update

    I'm using netctl's ifplugd service to automatically manage my network connections (LAN), however after latest update to netctl (1.10) I can not connect to other machines or internet anymore and I must downgrade to netctl 1.9.
    Related netctl service:
    [email protected]
    My network connection profile: /etc/netctl/mynetwork
    Description='A basic static ethernet connection'
    Interface=enp2s0
    Connection=ethernet
    IP=static
    Address=('192.168.1.1/24')
    #Routes=('192.168.0.0/24 via 192.168.1.2')
    Gateway='192.168.1.254'
    DNS=('192.168.1.254')
    ## For IPv6 autoconfiguration
    #IP6=stateless
    ## For IPv6 static address configuration
    #IP6=static
    #Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
    #Routes6=('abcd::1234')
    #Gateway6='1234:0:123::abcd'
    Related bits from journald:
    Jan 23 01:13:36 arch ifplugd[251]: ifplugd 0.28 initializing.
    Jan 23 01:13:36 arch ifplugd[251]: Using interface enp2s0/00:23:54:2C:CE:94 with driver <ATL1E> (version: 1.0.0.7-NAPI)
    Jan 23 01:13:36 arch ifplugd[251]: Using detection mode: SIOCETHTOOL
    Jan 23 01:13:36 arch ifplugd[251]: Initialization complete, link beat not detected.
    Jan 23 01:13:36 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
    Jan 23 01:13:36 arch acpid[246]: starting up with netlink and the input layer
    Jan 23 01:13:36 arch acpid[246]: 1 rule loaded
    Jan 23 01:13:36 arch acpid[246]: waiting for events: event logging is off
    Jan 23 01:13:37 arch kernel: floppy0: no floppy controllers found
    Jan 23 01:13:37 arch kernel: ATL1E 0000:02:00.0 enp2s0: NIC Link is Up <100 Mbps Full Duplex>
    Jan 23 01:13:37 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
    Jan 23 01:13:37 arch acpid[246]: client connected from 256[0:0]
    Jan 23 01:13:37 arch acpid[246]: 1 client rule loaded
    Jan 23 01:13:38 arch ifplugd[251]: Link beat detected.
    Jan 23 01:13:39 arch ifplugd[251]: Executing '/etc/ifplugd/netctl.action enp2s0 up'.
    Jan 23 01:13:39 arch ifplugd[251]: client: <3>Could not start any suitable profile
    Jan 23 01:13:39 arch ifplugd[251]: Program execution failed, return value is 1.

    This problem hit me too. I have a static IP address set up on a server, I upgraded netctl to 1.10 and it took me a couple of hours to work out why, after the upgrade, my network would not work. The messages were not helpful as I performed netctl starts, stops and status, or ip link commands. In the end I got the server back up by using ifconfig, ip addr add, ip route add etc. Then I found this forum entry (Thank you siavashserver and jouke!).
    While the solution can be found in the netctl manual, it is a little obscure. I think this deserves the status of a bug. I don't think a simple upgrade should allow a whole class of users (everybody with a static ip address) to lose network connectivity without warning.
    Even the (upgraded?) /etc/netctl/examples/ethernet-static file fails to include ExcludeAuto=no, so the documentation (at least in this regard) is faulty.
    When I performed the upgrade I was warned
    New optional dependencies for netctl
        openvswitch: for Open vSwitch connections
        ppp: for PPP connections
    Is it possible to add a message there saying Warning! If you have a static ip address, this upgrade will destroy your network connectivity next time you reboot unless you add ExcludeAuto=no to your network profile?
    jouke wrote:Add ExcludeAuto=no to your profile. As there is no way to check a statically configured IP address for correctness, they are excluded from automatic profile selection by default starting netctl 1.10. I am sorry for the inconvenience. From netctl 1.10 onwards, the behavior of netctl-ifplugd@ is documented in the man pages. For more information on ExcludeAuto= and Priority=, consult netctl.profile(5).

  • HT1849 what can i do if there's a song thats not playing it properly after purchased

    the song i purchased on itunes was not playing properly as it suppose to. so is there any way i can fix that?

    Delete and redownload it if doing so is free in your country.
    (105790)

  • MacBook Pro does not start up properly after yosemite, I see a black screen. What to do?

    Apple MacBook Pro 15 " 2.4iC2D/2x1Gb/160Gb/256V, 07-02-2008, always properly updated.
    Lately Iphoto worked slow and stuck many times. After ugrade from Maverick to Yosemite had to upgrade IPhoto as well.
    After that the laptop started 2 or 3 times, after that it showed me a black screen.
    I succeeded to connect with a firewire cable the laptop to my Mac and could look into the laptop.
    Unfortunately there was a power break, and I don't succeed in reconnecting.
    The laptop stays warm and I hear (I suppose) the hard disk.
    What to do? I want to find my fotos and put them on the Mac.

    I went to apple today and they told me that the hard drive has unmounted itself. They have my macbook right now and they said they're going to replace the wire that connects the hard drive to the logic board and see if this solves the issue. If it doesn't work they will replace the existing 250GB hard drive in my macbook with a 500GB as they no longer make that size hard drives (cost of £130 for the replacement). The problem is that i dont have my macbook backed up so will there be anyway to get data off the od hard drive?

  • I can not open itunes properly after upgrading to IOS7, the app appear blank. Any suggestion?

    After upgrading my iphone 5 to IOS 7.0.2, itunes does open properly. The app appear almost blank as it is hang up condition. Does anyone have a suggestion to solve this?

    Hi,
    Close the App Store app and the iTunes app by pressing the Home button twice, and swiping them up.
    Then go to Settings > Safari > Clear Cookies and Data
    Open the apps again.
    I'd recommend as well to sign out and in using Settings > iTunes & App Store
    Hope that helps.

  • I can not reboot my computer after suspend

    Last night I suspend my computer and today in the morning I wake it up ,but It's a little bit slow so I reboot it,and my tragedy comes...I can not reboot,it keeps showing like this :  http://paste.ubuntu.org.cn/100586 ,please help me ....
    Regards.
    ===================
    PS:English is not my mother tongue,forgive my syntax fault...

    Do you mean reboot, or you cannot bootup at all?
    Intel-based Macs: Resetting the System Management Controller (SMC)...
    http://support.apple.com/kb/HT3964

  • Windows 7 Pro not finding network connections after boot camp installation. Is there something special we have to do to get the network (wired and wireless) set up?

    Any suggestions for getting the network connections working on Windows 7 Pro running on a Mac Min with OSX Lion?

    tim-bob wrote:
    Any suggestions for getting the network connections working on Windows 7 Pro running on a Mac Min with OSX Lion?
    If you haven't yet installed the Windows Support Software, that's probably why, so install it now.

Maybe you are looking for