Weird issue starting network at boot [Solved]

So, whenever i bootup, when it comes to starting the network, it hangs for a few seconds, then says 'fail', however, whenever i get gnome up and working, the connection is working just fine, so far, i have tried to increase the timeout though it doesn't really seem to make it wait any longer during boot...here is my rc.conf if it helps anyone, also, i am trying to connect to some NFS shares from my freeNAS box on boot, but since that fails, the network shares normally do to, but after booted, i can just do mount -a and they all connect just fine...its weird
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="America/Chicago"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(sky2 slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !usblp)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.2.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng dbus hal fam network rpcbind nfs-common netfs crond)
also, i do have 'myhost' added to my hosts file as well, did so during setup...
anyone got any ideas?
Thanks
Last edited by psilo357 (2009-12-21 00:02:46)

alright, if just backgrounded 'network' it woudl cause rpcbind to start after it, but fail, so i backgrounded them all, and while network no longer says FAIL while booting, the network drives still don't mount, i still have to issue a mount -a after boot to get everything mounted...
thanks for the tip though. I don't mind it not running in background and waiting an extra few seconds to get everything setup as i want it to be as soon as i am logged in, just want it to all start correctly.
EDIT: alright, all network drives ARE mounting correctly on boot if nothing is in background, but i still don't like that network says FAIL when it is starting up, though it is apparently working...
all help is appreciated.
Last edited by psilo357 (2009-12-19 20:31:27)

Similar Messages

[Solved] Network does not starts on every boot

Yet another problem on fresh arch...
Network service does not starts every time I booting my headless. For every 10 attempts service starts 5 or 6 times only.
Ping says: Networking unreachable.
systemctl status network:
network.service - Static IP Connectivity
Loaded: loaded (/etc/systemd/system/network.service; enabled)
Active: inactive (dead)
'systemctl start network' just hangs. In order to get it start I have to reboot the box hoping next boot service will start.
I am not using dhcp (if it makes a sence). Service was configured as described in wiki for static IP assigning.
The config itself:
[Unit]
Description=Static IP Connectivity
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-enp4s1.device
After=sys-subsystem-net-devices-enp4s1.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ip link set dev enp4s1 up
ExecStart=/sbin/ip addr add 192.168.1.5/24 dev enp4s1
ExecStart=/sbin/ip route add default via 192.168.1.1
ExecStop=/sbin/ip addr flush dev enp4s1
ExecStop=/sbin/ip link set dev enp4s1 down
[Install]
WantedBy=multi-user.target
What's wrong?
Thanks in advance for any help.
Last edited by chord (2013-06-03 17:04:55)

Thaks for your reply.
I got this interface name from ip addr, how it should be named if 'enp4s1' is wrong?
journalctl is here: http://bpaste.net/show/104083/
I found only one string realted to this device name:
Jun 03 15:18:23 localhost systemd[1]: Expecting device sys-subsystem-net-devices-enp4s1.device...
Is there some other logs where it can be checked?

[Solved]Can't get past "Starting network" during installation from USB

I'm trying to do a fresh install of Archlinux on my laptop, following the Beginners Guide. However, I never get to the shell prompt because the installation gets stuck at "Starting network [Busy]".
These are steps I followed:
- I downloaded the latest Arch ISO.
- I wrote it to a usb stick ("Kingston Data Traveler") with "dd if=archlinux.iso of=/dev/sdb"
- I put the usb stick into my laptop (HP Pavilion dm1-4139sd), and booted it. I chose "x86_64". Everything seems to go fine, the only warning I get is: "microcode: failed to load file amd-ucode/microcode_amd.bin".
- I get the message "INIT: Entering runlevel: 3" and "Starting Syslog-NG [Done]", after that its endlessly (at least 20 minutes) stuck on "Starting network [Busy]".
I tried the following variations on the above:
- Wrote the ISO to a different USB, samen problem.
- Tried it with a different Arch version (from August), same problem.
- Turned kvm on and off, same problem.
- Pressed TAB at the "x86_64" line and added "acpi=off" to the end of it. I then get:
:: Triggering uevents....
[ 19.697932 ] usb 1-1: device not accepting address 2, error -110
:: Mounting '/dev/disk/by-label/ARCH_201209' to '/run/archiso/bootmnt'
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201209
[ 35.312165 ] usb 1-1: device not accepting address 3, error -110
[ 45.821422 ] usb 1-1: device not accepting address 4, error -110
[ 56.330681 ] usb 1-1: device not accepting address 5, error -110
[ 56.330681 ] hub 1-0:1.0: unable to enumerate USB devices on port 1
ERROR: '/dev/disk/by-label/ARCH_201209' device did not show up after 30 seconds....
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty; job control turned off
[rootfs /]#
I'm not sure what to do in this prompt. At least the network isn't working and none of the normal commands.
- I reset the DHCP leases on my modem, same problem.
- I turned off/on the hardware WLAN, same problem.
- I tried it with or without the LAN cable plugged in, same problem.
- I tried it with or without the battery plugged in, and with or without the power cable plugged in. Same problem.
I also performed the Arch memory test, and the bios hard disk test. They both report no errors.
I did an Arch installation a month ago on this laptop, and back then it didn't have this problem. I still have that arch installed from back then and it boots/works without problem (I have Starting NetworkingManager [Done]). I know I technically don't need to install arch again, as I still have the old one, but I wanted to clean the changes I made to some settings files and I if it turns out this is some kind of hardware problem I'd like to return it to the store.
Please help! I'm not really that familiar with Linux in general, so it might have been a very basic mistake from me as well. I have no idea what to do next, except for formatting my harddisk (which I don't think should influence the installer?), or trying to install a different Linux distro.
Edit: The solution that solved this problem for me in the end was resetting the BIOS to its defaults.
Last edited by dbakker (2012-09-15 11:28:14)

DSpider wrote:Did you check the MD5 checksum? If you downloaded it using a BitTorrent client, then you don't need to (its hash is checked during downloading).
Yes, I downloaded it using BitTorrent and the MD5 matches.
DSpider wrote:Try a different stick?
Yes, I tried it with 2 different USB sticks. They are both from the same brand ("Kingston DataTraveler"), so I might try different brands as well, but I don't think it is the problem.
DSpider wrote:Or at least a different method from that wiki page. For example, "dd"-ing it should work just fine.
The methods for writing the ISO that I tried so far:
The base method:
dd if=archlinux.iso of=/dev/sdb
(from an Arch install)
The method without overwriting your USB drive (created a FAT32 drive with an VFAT filesystem, from an arch install)
Using Imagewriter (from Windows)
Each method gives the same result: the laptop gets stuck at "Starting network [Busy]" when booted from one of the USB sticks. My modem indicates that it "sees" the laptop, but that the laptop has no established connection. When the laptop is stuck at the "Starting network [Busy]", all the activity on the USB stick stops (the light stops flashing).
The thing I find most strange is that the OS currently installed on the laptop has no problems booting or accessing the internet (both wired and wireless) at all.

[SOLVED] netctl not bringing up my network at boot

I recently converted from netcfg to netctl and but my network is not coming up ever at boot time. Once the machine is booted I can bring it up manually using
netcfg start ethernet-static
It is obviously an static IP address and I copied the netctl sample script and then modified it. Here is my ethernet-static profile.
Description='A basic static ethernet connection'
Interface=enp2s0
Connection=ethernet
IP=static
Address=('192.168.0.5/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='192.168.0.1'
DNS=('192.168.0.1')
## 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'
The output of journalctl -d | grep net is the following
un 14 08:40:03 kfrance-home kernel: Initializing cgroup subsys net_cls
Jun 14 08:40:03 kfrance-home kernel: audit: initializing netlink socket (disabled)
Jun 14 08:40:03 kfrance-home kernel: drop_monitor: Initializing network drop monitor service
Jun 14 08:40:03 kfrance-home systemd[1]: Expecting device sys-subsystem-net-devices-enp2s0.device...
Jun 14 08:40:03 kfrance-home kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Jun 14 08:40:03 kfrance-home kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
Jun 14 08:40:03 kfrance-home systemd-udevd[171]: renamed network interface eth0 to enp3s0
Jun 14 08:40:03 kfrance-home systemd-udevd[168]: renamed network interface eth0 to enp2s0
Jun 14 08:40:07 kfrance-home network[253]: Starting network profile 'ethernet-static'...
Jun 14 08:40:12 kfrance-home network[253]: No connection on interface 'enp2s0'
Jun 14 08:40:12 kfrance-home network[253]: Failed to bring the network up for profile 'ethernet-static'
Jun 14 08:40:12 kfrance-home systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exited, status=1/FAILURE
Jun 14 08:40:12 kfrance-home systemd[1]: Failed to start A basic static ethernet connection.
Jun 14 08:40:12 kfrance-home systemd[1]: Unit netctl@ethernet\x2dstatic.service entered failed state.
Jun 14 08:47:53 kfrance-home sudo[1300]: kfrance : TTY=pts/1 ; PWD=/home/emily ; USER=root ; COMMAND=/usr/bin/netctl start ethernet-static
Jun 14 08:47:53 kfrance-home systemd[1]: Starting A basic static ethernet connection...
Jun 14 08:47:53 kfrance-home network[1307]: Starting network profile 'ethernet-static'...
Jun 14 08:47:57 kfrance-home network[1307]: Started network profile 'ethernet-static'
Jun 14 08:47:57 kfrance-home systemd[1]: Started A basic static ethernet connection.
Nothing from netcfg, or any other network service, is leading to a conflict for configuring the network.
systemctl list-units | grep net
[email protected] loaded active exited A basic static ethernet connection
network.target loaded active active Network
I do have two ethernet ports but from what I can tell the naming of the two ports is consistent.
netctl status shows that my ethernet-static profile is the only profile and is active.
I know I could connect without using netctl but want to get this working. Any ideas?
Last edited by kfrance (2013-06-15 04:12:06)

I fixed the problem. I changed the device name of the ethernet device I wanted to use using an udev-rule, according to the notes on the Network Configuration wiki page, to make sure that it wasn't a naming conflict and that solved it.

Have to manually start network . . .[solved]

Hi,
For some reason my network doesn't start when I boot, but works fine when I run dhcpcd after logging in. I presume this is something simple, but would appreciate some help.
The module I need is 8139too. mkinticpio's autodetect gives 8139cp and 8139too for some reason, so I sorted that out in rc.conf. (It didn't work when I left the modules alone, either).
Here the relevant parts:
MOD_BLACKLIST=(pcspkr 8139cp)
MODULES=(8139too )
lo="lo 127.0.0.1"
eth0="DHCP"
eth1="DHCP"
INTERFACES=(lo eth0 eth1)
#gateway="default gw 192.168.0.254"
ROUTES=(!gateway)
DAEMONS=(syslog-ng !hotplug !pcmcia hal network @fam @portmap @netfs @crond @alsa)
I have network in the daemons array, but on startup it says 'cannot find device' (can't remember the exact wording) when trying to connect the network, as if the module isn't loaded yet, perhaps? Should something be loaded before network in the daemons?
The other thing is that I have eth0 and eth1 despite having only one network device (insofar as I'm aware) - ought this be the case? I just stuck eth1 into rc.conf blindly since it existed.
Any ideas on how to fix this?
Thanks.
Fishonadish

Don't know wether it belongs to rc.conf, too.
But UNIX is case-sensitive. Try to replace this line:
eth0="DHCP"
by
erh0="dhcp"
And all others that contain capitalized "DHCP".
And why do you connect via dhcp through two network interfaces?

How to solve the issue "OEL 5.6 boot Oracle ASMLib driver: FAILED" ?

Folks,
Hello. I am installing Oracle 11gR2 RAC using 2 VMs (rac1 and rac2) whose OS are Oracle Linux 5.6 in VMPlayer.
I downloaded Oracle Linux 5.6 Media Pack for x86_64 (file name V24479-01) from https://edelivery.oracle.com/linux.
I have installed OEL 5.6 for VM rac1 and done the follows:
1) install rpm and oracleasm packages for rac1.
2) edit /etc/hosts to set up IP addresses for eth0 and eth1 for rac1 and rac2.
3) edit eth0 and eth1 for rac1 by using command [root@rac1 \]# neat
But when boot the OS, I see "initializing Oracle ASMLib driver: FAILED".
When configure Oracle ASM library driver by running the command:
[root@rac1 /]#/etc/init.d/oracleasm configure -i
Its output "initializing Oracle ASMLib driver: FAILED"
I think the reason is the OS cannot initialize Oracle ASMLib driver. My question is:
Do any folk understand how to solve the issue "OEL 5.6 boot Oracle ASMLib driver: FAILED" ?
Thanks.

Folks,
Hello. Thanks a lot for replying. OEL 5.6 comes with 2 kernels: uek and red hat
I have chosen to use red hat kernel for 64-bit. I run the following command:
[root@rac1 /]# uname -rm
Output: 2.6.18-238.el5x86_64
I have downloaded 4 files for this version of kernel from
http://www.oracle.com/technetwork/server-storage/linux/downloads/rhel5-084877.html as below:
oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5-debuginfo-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm
I have installed the 4 files and got the error messages for the first 2 files as below:
[root@rac1 /]# rpm -ivh /home/oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
Error: Failed dependencies: kernel-xen=2.6.18-238.el5 is needed by oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
[root@rac1 /]# rpm -ivh /home/oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
Error: Failed dependencies: kernel-debug=2.6.18-238.el5 is needed by oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
The last 2 files have been installed successfully. But when reboot Oracle Linux Server-Base 2.6.18-238.el5, I still see :
"Initializing ASMLib driver: FAILED."
[root@rac1 /]#/etc/init.d/oracleasm configure -i
Its output "initializing Oracle ASMLib driver: OK "
My questions are:
Does the issue OS "Initializing Oracle ASMLib driver: FAILED" have effect later ? Do we need to solve it ?
Thanks.

[SOLVED] Scan for wireless networks at boot

Lately I've been making extensive use of public wifi hotspots (libraries FTW), as mobile broadband is simply too unreliable to give me a persistent (and cheap) connection.
Is it possible to use some combination of netcfg and wifi-select (or similar tools) to scan for wireless networks at boot?
I've already got entries in rc.conf for my mobile dongle and automatically detecting ethernet connections, but it's pointless adding entries for whichever wireless profiles I might use as searching for these and discovering they don't exist just needlessly slows the boot process, whereas running something similar to wifi-select at boot (with a timeout so an unattended boot won't wait for me to make a selection) would avoid this.
* Obviously I could just wait until the system has booted and then bring up the interface I wanted manually, but generally I only reboot my system after updates, and I only download updates at a wifi hotspot, so I was hoping to automate something here.
Last edited by zoqaeski (2012-03-28 12:11:21)

Isn't net-auto-wireless or net-profiles with menu what you want? https://wiki.archlinux.org/index.php/ne … omatically

[SOLVED] kdemod with ugly cyan boarders / can't start kdm at boot?

I followed the directions to install kdemod from a clean installation of Arch Linux. Specifically I:
Installed from CD
Setup DHCP and configured my ethernet
Updated Arch Linux ( pacman -Syu )
Installed xorg
installed hdw and configured xorg
setup repositories to include kdemod repos
installed kdemod, as well as some recommended additions
if I follow any of the directions here ( http://chakra-project.org/download-kdemod-step6.html ) to start kdemod at boot then it gives me a login prompt but immediately crashes and restarts kdm whenever I login. I can only get into kdemod by typing, in the console: startx
and then: startkde
...and then all of my windows are surrounded by ugly monotone cyan window decorations which look like they came out of Windows 3.1 that I can't seem to get rid of, as well as a few other oddities involving the color cyan.
I am, incidentally, running it in VirtualBox with the vesa video driver in xorg.conf.
Does anyone know what's going on? Am I missing something? Is this normal?
I've found one mention of this problem on the forums before [ http://bbs.archlinux.org/viewtopic.php?pid=494261 ] but no solution. Thanks in advance.
Last edited by thorjelly (2009-02-15 03:48:05)

Alright, I figured out where those ugly cyan borders come from. It's because I didn't make an .xinitrc file in my user's directory and specify what window manager to use, so it defaulted to xterm, and I was running kde through xterm and the borders were xterm's window borders (Right, well, I figured they were a biproduct of running kde in such an unusual way)... but I still don't know why I can't start kdm at boot. Anyone know how I can figure that out...?
Last edited by thorjelly (2009-02-15 03:35:44)

Dhcpcd does not start automatically on boot

Hi everyone,
I have just installed Arch (64 bit) and am running on a dynamic, wired connection.
I followed the Beginners' Guide and enabled the dhcpcd service during the installation so that it would start automatically on boot.
systemctl enable [email protected]
However, I currently must issue the command "dhcpcd" each boot before the internet starts to work.
Does anyone know how I can automate this process or if I need to further configure my network connection?
Thank you in advance.
Last edited by Ipozya (2012-11-15 11:29:05)

foppe wrote:
Check the output from
# systemctl status [email protected]
to debug the issue you're experiencing.
% sudo systemctl status [email protected]
[email protected] - dhcpcd on eth0
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-15 20:38:16 GMT; 27 sec ago
Process: 244 ExecStart=/sbin/dhcpcd -A -q -w %I (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/[email protected]/eth0
Nov 15 20:37:47 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:47 arch dhcpcd[244]: eth0: sendmsg: Cannot assign requested address
Nov 15 20:37:47 arch dhcpcd[244]: eth0: broadcasting for a lease
Nov 15 20:37:51 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:55 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:59 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:59 arch dhcpcd[244]: eth0: no IPv6 Routers available
Nov 15 20:38:16 arch dhcpcd[244]: timed out
Nov 15 20:38:16 arch systemd[1]: Failed to start dhcpcd on eth0.
Nov 15 20:38:16 arch systemd[1]: Unit [email protected] entered failed state
Dhclient did not work automatically on boot either.
Others seem to have experienced similar issues but I don't see any real solutions in any of these posts, despite being marked as solved. For example, adding "-t 120" to the dhcpcd start line in /usr/lib/systemd/system/[email protected] did not work for me.
I also tried the following but it did not work either and I had to issue "dhcpcd" before internet started working.
Install and configure wired and wireless networking
# pacman -S netcfg ifplugd
# cd /etc/network.d
# ln -s examples/ethernet-dhcp .
Make sure the WIRED_INTERFACE and WIRELESS_INTERFACE lines is uncommented
# nano /etc/conf.d/netcfg
# systemctl enable net-auto-wired.service
# pacman -S wireless_tools wpa_supplicant wpa_actiond dialog
# systemctl enable net-auto-wireless.service
https://bbs.archlinux.org/viewtopic.php?pid=1176656
https://bbs.archlinux.org/viewtopic.php?pid=1189587
https://bbs.archlinux.org/viewtopic.php?pid=1180192
Last edited by Ipozya (2012-11-15 21:08:03)

Weird Issues when Internet Connection not working

I hope I'm posting this in the correct forum.
This morning, my internet connection was not working (a common issue, whatever it is that requires me to restart my router. Tubes clogged, etc etc. I could ping it, but not get out). Anyways, before I restarted the router and restored internet connectivity, my machine took forever to boot and start X. During boot, it would hang at starting the CUPS daemon for a good 20-30 seconds. Then, it would eventually start and the machine would boot to agetty. I could log in fine, but when I typed 'startx' the machine would do nothing for about 5 seconds, and then X would start as per usual. Note that after issuing the startx command I got no output at all to stdout until after the delay.
Question: Why did this happen? My best guess is that on these occasions the machine was trying to connect to the outside world, and it was only after a network timeout that things went ahead as usual. But, that hardly makes any sense to me, for a couple of reasons. Why would CUPS and startx try to connect to the outside? The lag in starting CUPS was considerably longer than when issuing startx. The lag for startx did not seem long enough for a timeout. Weird. Any clarification would be helpful.
Last edited by hbarnwheeler (2009-04-13 14:26:25)

It might something wrong with the IP addressing you used when you statically set the configuration or traffic from the IP address you used is denied.
As you already have an IP config that works (Run ipconfig /all to get it) then you can simply proceed using one of these ways:
On your DHCP level, do a reservation of the IP address so that it will always be allocated to your server
or on your DHCP level, exclude the IP address of the server and set it manually on the server
More information if you contact your Network Engineer for assistance.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

I can't seem to get my iMac (late 2009 model) into automatic sleep mode. If I manually put it into sleep I don't have any issues. I used to solve the issue by running "PleaseSleep" application but that doesn't work anymore since Lion.

I can't seem to get my iMac (late 2009 model) into automatic sleep mode. If I manually put it into sleep I don't have any issues.
I used to solve the issue by running "PleaseSleep" application but that doesn't work anymore since Lion. I now want to fix the underlying problem.
I'm not running any weird background processes and in my energy saver settings I've tagged "put the hard disk to sleep when possible:, "allow power button to put computer to sleep" and "automatically reduce brigthness". All pretty standard.
Is there anyone who can give me some pointers ?

Today I solved the same problem for my iMac running Snow Leopard. See https://discussions.apple.com/thread/3008791#15947706. The method may help you, too.
For me it was the DynDNS Updater preventing my iMac from automatically entering sleep mode.
To my knowledge the cause of this sleep problem can only be a peripheral device or a process. So I suggest to first unplug all peripherals and test whether that's the cause. If not, I suggest to terminate one process after another and to test automatic entering of sleep mode after each. Start with user processes; continue with system process if necessary.
At least that's the way I found the offending process. Fortunately, I was able to change the configuration of that process to allow again automatic entering of sleep mode.
Good luck!

Flex 4.5 weird issue

Hi All,
I have encountered a weird issue after I migrated my application from flex 3.5 to flex 4.5.
In our application, we have 3 kind of views, View, ChartView and StackedView, the later extends the former one, let's say, in ChartView we have
<local:View...>....</local:View>, in StackedView we start with <local:ChartView>. We config the view type in the database as View.swf, ChartView.swf and StackedView.swf. The problem here is for example, if I load a view with StackedView.swf and change to a view with ChartView.swf, some of the components will not initialized, we get runtime exception like
ArgumentError: Error #2004: One of the parameters is invalid.
    at flash.display::Graphics/drawRect()
    at mx.controls::VRule/updateDisplayList()[E:\dev\4.5.1\frameworks\projec ts\mx\src\mx\controls\VRule.as:256]
    at mx.core::UIComponent/validateDisplayList()[E:\dev\4.5.1\frameworks\pr ojects\framework\src\mx\core\UIComponent.as:8989]
    at mx.managers::LayoutManager/validateDisplayList()[E:\dev\4.5.1\framewo rks\projects\framework\src\mx\managers\LayoutManager.as:736]
    at mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\4.5.1\frame works\projects\framework\src\mx\managers\LayoutManager.as:801]
    at mx.managers::LayoutManager/doPhasedInstantiationCallback()[E:\dev\4.5 .1\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1180 ]
We debugged into the code, and found that the exception occoured before the parent component is initialized. Actually the parent(or the parent's parent) component's height or width is NaN.
By the way, if we load ChartView.swf directly, everything works perfectly.
And I just solved the problem by spliting the 3 type of views, say, keep the View.swf, comibine the code from View.swf with ChartView.swf to a new ChartView.swf, the same to StackedView.swf, which now combines 3 type of views' code.
Though the problem is solved, but everyone can see it's not an elegent way, and the maintenence cost is high.
I suspect it is something related to load module or unload module, seperating the 3 type of views just make sure they didn't share something.
Can any expert help me figure this out? Many thanks.

Use the profiler to see what is hanging onto the old memory. But my main point is not about memory. It is about sizes. An empty container has no default size. When it gets a child it often picks the child size, and then if that child is removed and another child is provided, instead of picking that new child’s size, it might still use the old child’s size, and that might cause the new child to layout at a different size than if it was the first child.

LaCie ext drives not starting up on boot

I have 4 LaCie drives that do not automatically turn on mount when I power up my tower:
2TB LaCie BIGGER U2&F4&F8 EXTR 7200RPM 16MB US
Big Disk
d2 Hard Drives
When I have connected my older 17" PowerBook, the drives start up on boot and turn off at shutdown as they should. This action also occurred successfully on my previous G5 tower running Tiger. This is not occurring on my current G5 tower (Mac Pro).
Both systems are running Leopard, but the 17" PB is NOT the Intel processor like the tower.
All firmware has been updated on the external drives per LaCie's instructions, and they are now suggesting I turn this issue over to Apple to figure out.
The drives work fine, and I can turn them on manually when I boot the machine, but I just want my automatic turn on and turn off back.
Suggestions?

Ok here's the output after a fresh boot.
ben@arch-desktop:~$ systemctl status [email protected] -l
[email protected] - PS3 Media Server
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
Active: active (running) since Wed 2014-03-05 22:20:11 EST; 1min 8s ago
Main PID: 601 (java)
CGroup: /system.slice/system-pms.slice/[email protected]
└─601 java -Xmx768M -Xss1024k -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djna.nosys=true -classpath update.jar:pms.jar net.pms.PMS
Mar 05 22:20:20 arch-desktop PMS.sh[601]: at java.lang.Thread.run(Thread.java:744) [na:1.7.0_51]
Mar 05 22:20:21 arch-desktop PMS.sh[601]: ERROR 2014-03-05 22:20:21.264 [UPNPHelper] UPNP network exception
Mar 05 22:20:21 arch-desktop PMS.sh[601]: java.net.SocketException: No such device
Mar 05 22:20:21 arch-desktop PMS.sh[601]: at java.net.PlainDatagramSocketImpl.join(Native Method) ~[na:1.7.0_51]
Mar 05 22:20:21 arch-desktop PMS.sh[601]: at java.net.AbstractPlainDatagramSocketImpl.join(AbstractPlainDatagramSocketImpl.java:178) ~[na:1.7.0_51]
Mar 05 22:20:21 arch-desktop PMS.sh[601]: at java.net.MulticastSocket.joinGroup(MulticastSocket.java:319) ~[na:1.7.0_51]
Mar 05 22:20:21 arch-desktop PMS.sh[601]: at net.pms.network.UPNPHelper$2.run(UPNPHelper.java:384) ~[pms.jar:1.90.1]
Mar 05 22:20:21 arch-desktop PMS.sh[601]: at java.lang.Thread.run(Thread.java:744) [na:1.7.0_51]
Mar 05 22:21:05 arch-desktop PMS.sh[601]: INFO 2014-03-05 22:21:05.376 [UPNPHelper] No IP filter specified, access granted to /192.168.1.42
Mar 05 22:21:05 arch-desktop PMS.sh[601]: INFO 2014-03-05 22:21:05.377 [UPNPHelper] Using the following UUID configured in PMS.conf: 6ed45cde-e5fa-4e6b-a419-306a122aba82

Systemd.timesyncd fails on boot [Solved]

Upgraded systemd to 217-1 and now each boot sees timesyncd fail:
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-10-31 10:25:59 NZDT; 5min ago
Docs: man:systemd-timesyncd.service(8)
Process: 303 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
Main PID: 303 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Oct 31 10:25:59 Shiv systemd[1]: start request repeated too quickly for systemd-timesyncd.service
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Once I log in, I am able to restart the service without any complaint.
Anyone else seeing this?
# edit: perhaps related to this fixed(?) bug: http://lists.freedesktop.org/archives/s … 03199.html

tl;dr answer:
# sed -i 's/ remote-fs.target$//' /usr/lib/systemd/system/systemd-journal-flush.service
Long answer:
In systemd 217 a few changes were made with regard to ordering of early boot units, resulting in certain setups which used to work with systemd 216 to make problems with systemd 217. The fix above was also applied in systemd upstream by this commit:
commit 919699ec301ea507edce4a619141ed22e789ac0d
Author: Lennart Poettering <[email protected]>
Date: Fri Oct 31 16:22:36 2014 +0100
units: don't order journal flushing afte remote-fs.target
Instead, only depend on the actual file systems we need.
This should solve dep loops on setups where remote-fs.target is moved
into late boot.
For example, in my case, connman.service explicitly requests to be ordered before remote-fs.target, leading to all kinds of fun:
systemd[1]: Found ordering cycle on basic.target/start
systemd[1]: Found dependency on sysinit.target/start
systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
systemd[1]: Found dependency on systemd-journal-flush.service/start
systemd[1]: Found dependency on remote-fs.target/start
systemd[1]: Found dependency on connman.service/start
systemd[1]: Found dependency on basic.target/start
systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start
systemd-timesyncd[201]: Failed to allocate manager: No such file or directory
systemd[1]: systemd-timesyncd.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Network Time Synchronization.
systemd[1]: Unit systemd-timesyncd.service entered failed state.
systemd[1]: systemd-timesyncd.service failed.
Explanation:
systemd-journal-flush.service wants to be ordered after remote-fs.target whereas connman.service wants to be ordered before remote-fs.target. Additionally, connman.service requires basic.target. (This is implicit behavior for units which don't declare "DefaultDependencies=no".) This is why basic.target ends up getting pulled in so early in the first place.
Furthermore, systemd-timesyncd.service relies on properly initialized runtime directories in order to work, so it wants to be ordered after systemd-tmpfiles-setup.service.
In order to be able to start basic.target, systemd breaks the ordering cycle by taking systemd-tmpfiles-setup.service out of the transaction, thereby preventing systemd-timesyncd.service from starting up correctly.
Last edited by csn (2014-11-01 22:18:37)

Weird issue with Site Template in O365

Hi,
I ran into a weird issue while working with Site Template in O365 last night.
I created a sub-site in a Site Collection with some Site Columns, CT and Lists. Then I saved it as a Site Template so that it can be used for different sites. Then I created 3 different sub-sites using the template. All went good.
After some time when I looked at the sites, something really irritating happened. I saw the first two sites were missing all the site columns and CT. And the latest third site had 3 copies of each Site Column and CT. Though for the first two sites,
all the CT, Site Columns were available at List level, but it wad just the reference. The Actual CT was not seen the site settings.
This is the first time I saw this kind of issue. Not sure what is the reason for this.
Any idea around this ?
Thanks,
Nutan
Nutan Sharma

Hi,
According to your description, my understanding is that the error occurred when you created a site from the template with no files in the document library.
I tested the same scenario per your post, and I can create a site from the template with no files in the document library with no errors.
To solve this issue, I recommend to verify the things below:
Did you save the site as a template with Include Content checked? If yes, I recommend to test if it works when saving the site as a template with Include Content unchecked.
Test the same scenario with a new site to narrow the issue scope.
I also recommend to check the event log and ULS log to see if anything unexpected occurred.
To check event log, click the Start button and type “Event Viewer” in the Search box.
For SharePoint 2010, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS.
You can check the ULS log by the methods here:
http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx
http://msdn.microsoft.com/en-us/library/gg193966(v=office.14).aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Weird issue starting network at boot [Solved]

Similar Messages

Maybe you are looking for