Network fails every other boot [SOLVED]

I seem to have a small prob when I startup my pc the network fails every other time. I had some probs w/ dhcp starting when I used gentoo, and found a workaround, putting "dhcpcd -k" in etc/conf.d/local.stop ran the dhcpcd -k command when I shutdown my pc, apparently arch's syntax is a bit different so I doubt etc/conf.d/local.stop exists, I tried /etc/rc.local.shutdown, but that didn't seem to do it either. Could someone please tell me the arch way to enter this command every shutdown?

Snowman wrote:
Haiyadragon wrote:
I'm having the same problem. My motherbord has two network devices. It seems that the designations (eth0 and eth1) switch every boot. So every other boot eth0=dhcp is the right one.
Will "dhcpcd -k" fix it?
Check this: http://wiki.archlinux.org/index.php/Ude … _Each_Boot
Thanks.
Altough I find it quite weird they switch like that.
"Because udev loads all modules at once, devices are sometimes initialized in a different order. For example, with two network cards, you may notice they switch designations between eth0 and eth1"
Yeah, I don't buy it. They switched every boot.
I'm trying the udev-sanctified method. Will find out in a day or so (when I (re)boot).

Similar Messages

Netctl wireless fails every other boot [SOLVED]

This has me stumped.
Here is my netctl profile:
gdm@gdmThink ~$ cat /etc/netctl/mifi4510l
Description='A simple WPA encrypted wireless connection using a static IP'
Interface=wlp3s0
Connection=wireless
Security=wpa
ESSID='Verizon MIFI4510L E3A0 Secure'
Key='password'
IP=static
Address='192.168.1.11/24'
Gateway='192.168.1.1'
DNS=('192.168.1.1')
TimeoutWPA=30
Here is a pastebin link to the "journalctl -b" for a failed boot:
http://pastebin.com/GbELjqm0
Here is a pastebin link to the "journalctl -b for a successful boot.
http://pastebin.com/ywzDvkqD
Other than there is no attempt to authenticate in the failed boot, I see no significant difference.
Any help would be greatly appreciated.
Last edited by gdavid (2013-05-26 16:19:42)

[root@gdmThink gdm]# systemctl status -n 100 [email protected]
[email protected] - A simple WPA encrypted wireless connection using a static IP
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Sat 2013-05-25 17:57:53 EDT; 42s ago
Docs: man:netctl.profile(5)
Process: 830 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
[root@gdmThink gdm]#
From dmesg:
[ 11.726467] systemd[1]: Starting Login Service...
[ 11.726547] systemd[1]: About to execute: /usr/lib/systemd/systemd-logind
[ 11.726627] systemd[837]: Executing: /usr/lib/systemd/systemd-user-sessions start
[ 11.726685] systemd[1]: Forked /usr/lib/systemd/systemd-logind as 838
[ 11.726784] systemd[1]: systemd-logind.service changed dead -> start
[ 11.726799] systemd[1]: Starting D-Bus System Message Bus...
[ 11.726971] systemd[838]: Executing: /usr/lib/systemd/systemd-logind
[ 11.727515] systemd[1]: About to execute: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[ 11.727642] systemd[1]: Forked /usr/bin/dbus-daemon as 839
[ 11.727781] systemd[1]: dbus.service changed dead -> running
[ 11.727786] systemd[1]: Job dbus.service/start finished, result=done
[ 11.727923] systemd[839]: Executing: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[ 11.728498] systemd[1]: Started D-Bus System Message Bus.
[ 11.728602] systemd[1]: Set up jobs progress timerfd.
[ 11.728630] systemd[1]: Received SIGCHLD from PID 829 (alsactl).
[ 11.728645] systemd[1]: Got SIGCHLD for process 829 (alsactl)
[ 11.728674] systemd[1]: Child 829 died (code=exited, status=0/SUCCESS)
[ 11.728677] systemd[1]: Child 829 belongs to alsa-restore.service
[ 11.728685] systemd[1]: alsa-restore.service: main process exited, code=exited, status=0/SUCCESS
[ 11.728782] systemd[1]: alsa-restore.service changed start -> dead
[ 11.728841] systemd[1]: Job alsa-restore.service/start finished, result=done
[ 11.729552] systemd[1]: Started Restore Sound Card State.
[ 11.729583] systemd[1]: Got SIGCHLD for process 833 (modprobe)
[ 11.729609] systemd[1]: Child 833 died (code=exited, status=0/SUCCESS)
[ 11.729611] systemd[1]: Child 833 belongs to lm_sensors.service
[ 11.729618] systemd[1]: lm_sensors.service: main process exited, code=exited, status=0/SUCCESS
[ 11.729620] systemd[1]: lm_sensors.service running next main command for state start
[ 11.729652] systemd[1]: About to execute: /usr/bin/sensors -s
[ 11.729756] systemd[1]: Forked /usr/bin/sensors as 840
[ 11.729894] systemd[1]: Accepted connection on private bus.
[ 11.729900] systemd[1]: Incoming traffic on dbus.socket
[ 11.729908] systemd[1]: dbus.socket changed listening -> running
[ 11.729940] systemd[1]: Accepted connection on private bus.
[ 11.729978] systemd[1]: Accepted connection on private bus.
[ 11.729987] systemd[840]: Executing: /usr/bin/sensors -s
[ 11.730107] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 11.730151] systemd[1]: systemd-update-utmp.service: cgroup is empty
[ 11.730175] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 11.730195] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 11.730237] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 11.730264] systemd[1]: alsa-restore.service: cgroup is empty
[ 11.730282] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 11.730299] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 11.776646] systemd[835]: Executing: /usr/bin/laptop_mode init auto
[ 11.937296] systemd[1]: Received SIGCHLD from PID 837 (systemd-user-se).
[ 11.937318] systemd[1]: Got SIGCHLD for process 837 (systemd-user-se)
[ 11.937352] systemd[1]: Child 837 died (code=exited, status=0/SUCCESS)
[ 11.937354] systemd[1]: Child 837 belongs to systemd-user-sessions.service
[ 11.937366] systemd[1]: systemd-user-sessions.service: main process exited, code=exited, status=0/SUCCESS
[ 11.937490] systemd[1]: systemd-user-sessions.service changed start -> exited
[ 11.937494] systemd[1]: Job systemd-user-sessions.service/start finished, result=done
[ 11.938230] systemd[1]: Started Permit User Sessions.
[ 11.938264] systemd[1]: Starting Getty on tty1...
[ 11.938997] systemd[1]: About to execute: /sbin/agetty --noclear tty1 38400 linux
[ 11.939186] systemd[1]: Forked /sbin/agetty as 844
[ 11.939313] systemd[1]: [email protected] changed dead -> running
[ 11.939344] systemd[1]: Job [email protected]/start finished, result=done
[ 11.940070] systemd[1]: Started Getty on tty1.
[ 11.940089] systemd[1]: Starting Login Prompts.
[ 11.940092] systemd[1]: getty.target changed dead -> active
[ 11.940094] systemd[1]: Job getty.target/start finished, result=done
[ 11.940824] systemd[1]: Reached target Login Prompts.
[ 11.940886] systemd[1]: Accepted connection on private bus.
[ 11.941016] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 11.941058] systemd[1]: systemd-user-sessions.service: cgroup is empty
[ 11.941085] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 11.973600] e1000e 0000:00:19.0: irq 49 for MSI/MSI-X
[ 12.074517] e1000e 0000:00:19.0: irq 49 for MSI/MSI-X
[ 12.074737] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[ 12.074979] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 12.075190] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 12.425688] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 12.425894] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 12.464645] systemd[1]: Received SIGCHLD from PID 840 (sensors).
[ 12.464666] systemd[1]: Got SIGCHLD for process 840 (sensors)
[ 12.464701] systemd[1]: Child 840 died (code=exited, status=0/SUCCESS)
[ 12.464704] systemd[1]: Child 840 belongs to lm_sensors.service
[ 12.464716] systemd[1]: lm_sensors.service: main process exited, code=exited, status=0/SUCCESS
[ 12.464829] systemd[1]: lm_sensors.service changed start -> exited
[ 12.464838] systemd[1]: Job lm_sensors.service/start finished, result=done
[ 12.465943] systemd[1]: Started Initialize hardware monitoring sensors.
[ 12.466053] systemd[1]: Accepted connection on private bus.
[ 12.466244] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 12.466278] systemd[1]: lm_sensors.service: cgroup is empty
[ 12.466302] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 12.648245] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 12.648631] systemd[1]: Received SIGCHLD from PID 831 (dhcpcd).
[ 12.648648] systemd[1]: Got SIGCHLD for process 831 (dhcpcd)
[ 12.648680] systemd[1]: Child 831 died (code=exited, status=0/SUCCESS)
[ 12.648682] systemd[1]: Child 831 belongs to dhcpcd.service
[ 12.648688] systemd[1]: dhcpcd.service: control process exited, code=exited status=0
[ 12.648719] systemd[1]: dhcpcd.service got final SIGCHLD for state start
[ 12.648735] systemd[1]: Main PID loaded: 872
[ 12.648782] systemd[1]: dhcpcd.service changed start -> running
[ 12.648786] systemd[1]: Job dhcpcd.service/start finished, result=done
[ 12.650040] systemd[1]: Started dhcpcd on all interfaces.
[ 12.838952] systemd[1]: Received SIGCHLD from PID 830 (network).
[ 12.838973] systemd[1]: Got SIGCHLD for process 830 (network)
[ 12.839025] systemd[1]: Child 830 died (code=exited, status=1/FAILURE)
[ 12.839028] systemd[1]: Child 830 belongs to [email protected]
[ 12.839038] systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
[ 12.839042] systemd[1]: [email protected] changed start -> failed
[ 12.839129] systemd[1]: Job [email protected]/start finished, result=failed
[ 12.841013] systemd[1]: Failed to start A simple WPA encrypted wireless connection using a static IP.
[ 12.842353] systemd[1]: Unit [email protected] entered failed state.
[ 12.842373] systemd[1]: Starting Network.
[ 12.842377] systemd[1]: network.target changed dead -> active
[ 12.842382] systemd[1]: Job network.target/start finished, result=done
[ 12.843262] systemd[1]: Reached target Network.
[ 12.843299] systemd[1]: Accepted connection on private bus.
[ 12.843488] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 12.843531] systemd[1]: [email protected]: cgroup is empty
[ 12.843557] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 12.843759] systemd[1]: Accepted connection on private bus.
Sorry for the delayed response. I am in the middle of moving.

Netctl-auto fails every second boot

So, since about two oder three days ago, my netctl-auto fails every second boot and I can't even enable a profile manually.
I already found this thread: https://bbs.archlinux.org/viewtopic.php?pid=1275755
But I checked and don't have any failed units and dhcpcd is not running.
I will do some further investigation and post it here. Any ideas for solutions are welcome
Wolle

I've been having the same problem as well, it boots up just fine then after a reboot netctl-auto fails which had been going on for me for the past 30 minutes without "fixing" itself.
After I added the line:
TimeoutDHCP=30
to my profile then rebooted, it worked. It could be a fluke "fix" but worth a try. I *think* the reason it worked is that the default timeout is 10 seconds which might not be enough to establish a connection for some routers/network cards.
EDIT: I did another boot to see if it was a fluke, and it was. I'm getting a little tired of netctl-auto... I'm going to just disable it and manually do a "netctl start <profile>" after I boot up.
Last edited by DukeH (2013-07-16 19:07:58)

Touchpad Cannot Start Code 10 Every Other boot

Model: 3000 N100 768 A49
Symptoms: The touchpad device is unable to start code 10. Every other boot when runnign Windows 7 Beta and RC
Other associated symptom when this occurs is that the display resolution gets set to 640*480. Only resolution is to reboot.
This happens on a CLEAN INSTALL of both Beta and RC.
The mouse works perfectly thorough the installation process and initial boot.

On futher inspection I find that most drivers fail to load when this happens and there is a kernel-pnp warning in the logs for every driver that fails to load. I believe that it may be caused by an IRQ/APIC problem. If this is the case we may need a bios upgrade to support windows 7 on the N100. Which i dont think will happen considering lenovo has no vested interest in supporting consumer grade notebooks.
Is there anyone at lenovo I can contact to try and help resolve this? I have not received a single reply.
This problem is not common at all. I have only found one other similar thread and the notebook was an hp notebook.
Again the weird thing is that it happens every other boot.
When the computer is off i turn it on and drivers fail to load. Then i turn it off then back on and everything works fine.
However this does not happen with Vista.
If anyone is interested I can post the logs.

K7N2 Delta2 Does not Post Every Other Boot

I have built a PC with a K7N2 Delta2-LSR mb and it fails to post on every other boot. When it does post, everything works fine. It makes no difference whether the boot is warm or cold, and it does not vary in frequency (it is always every other boot).
Any ideas?

Hi, I have the same problem. (sorry for my english)
When i switch on my pc, nothing hapend.... freeze.... The power led and the hdd led on and the screen stay off. I need to unplug the power wire and then plug it again to turn on the pc.
Thanks for your time.
K7N2 Delta2 MS-6570E (v1.X) - BIOS Phoenix - AwardBIOS v6.00PG - Version : Nvidia - 42302e31
AMD XP 2700+ BOX - FSB 333 (with original FAN COOLER)
512mb DDR333
BIOSTAR G-FORCE FX 5200
1 HD S-ATA - Western Digital WDC WD800JD-00HKA0
1 HD IDE - Maxtor 6E020L0
1 DVD IDE - Sansung SD-6125
1 CD-RW IDE - SONY CRX230ED
PSU: BISWAL ATX 400w - KC-EAA
+12v 15 A
+5v 25 A
+3.3v 20 A
-5v 1 A
-12v 1 A
+5VSB 2 A
OS: XP Pro SP2
----------------------------- EN ESPAÑOL
Hola, tengo el mismo problema. Cada vez que reinicio o apago la pc, debo desenchufarle la electricidad para que encienda. Si la apago del switch y la vuelvo a encender sigue congelada. Ahora una vez que hago esto funciona perfectamente.
Gracias por tu tiempo.

IPASCII Response fails every other poll.

IPASCII Driver object is used to retrieve (via Ethernet) data.
Request format works good.
My Request Format (RequestFormat):
"GET /data HTTP/1.0 \r\n\r\n" as per device manufacture Txt string and
(2) carriage return/line feeds
Response String looks good Object = (.Response)
Typical Response String
F|74.0|29.3|-999.9|74.0|29.3|-999.9|-999.9|-999.9|-999.9|-999.9|-999.9
|-999.9
Data is temperature from module, -999.9 are data inputs without temperature
probes attached...
RSV1.txt = (F)
RSV2.txt = (74.0)
ETC...
RSV1-13 data look good but fails every other poll
(Socket communications error 10053: Software caused connection abort).

I have received the following response from NI engineers.
To review this issue -- the IPASCII object has a problem in that if you use the IPASCII object to query a web service that closes the
connection remotely after a request has been made Lookout will not close the local connection. This results in a "CLOSE_WAIT"
state for the local TCP port. Since the port is not closed, Lookout is not able to make a subsequent outgoing connection on the
same port. Lookout does appear to close the port when after it tries to make repeated connections, but this means for every time
you want to make a query you have to alternate between successful queries and comm failures. Most likely this was not found earlier
because for many Ethernet based instruments, a TCP connection is persistent, however web servers using the HTTP/1.0 protocol
close the TCP connection after every GET request and response. A corrective action request has been filed with our Lookout R&D
team and hopefully a fix will be available in future versions of Lookout. Thank you for your patience with this issue.

Deploying Windows Service Fails Every Other Time

I'm using Release Management 2013 to deploy a Windows service. I go through the steps listed below to deploy it. It fails on the first step (Delete Service) every other time. When I run it again, it works. It seems like it's saying
it failed, but is somehow actually succeeding. After it fails, I don't see the service in the Services list anymore. Then when I run the deployment again, it succeeds.
I have found that if I manually stop the service before deploying again, it will always succeed. There doesn't seem to be a good way of doing that in Release Management though, since the Stop Service action will error out if the service doesn't exist.
Any help would be appreciated!
==============
Delete Service
Create Folder
XCopy Site Deployment (deploys from drop folder)
Copy Config Files from Drop folder (copies config files folder from drop folder)
Delete File(s) or Folder (deletes existing config)
Rename File or Folder (renames appropriate copied config to the name of the previously deleted config file)
Delete File(s) or Folder (deletes other config files)
Delete File(s) or Folder (deletes config folder)
Create Service
Start Service

Hi,
You may have solved this by now, but for the record, I had the exact same issue. The problem is in this section of ManageWindowsServices.ps1
elseif ($Action -eq "delete")
#If the service exists, we first stop it to avoid "Marked for deletion" problems
$service = Get-Service -Name $ServiceName -ErrorAction SilentlyContinue
if ($service -ne $null)
#Stop the service
$status = & "sc.exe" "$ServerName" stop "$ServiceName"
"Stop status : $status"
$status = & "sc.exe" "$ServerName" $Action "$ServiceName"
"Delete status : $status"
#Ensure the service was deleted successfully
$service = Get-Service -Name $ServiceName -ErrorAction SilentlyContinue
if ($service -ne $null)
$(throw "The deletion of the service failed.")
else
$exitCode = 0
and is due to the fact that the second Get-Service call does actually return the service, even though it's after the call to delete it. Presumably this is some kind of race condition, where the call to delete the service returns before it's finished all
it's work.
In any case, the solution I went for was to rewrite this section as:
elseif ($Action -eq "delete")
[int]$returnCode = 0
#If the service exists, we first stop it to avoid "Marked for deletion" problems
$service = Get-WmiObject -Class Win32_Service -Filter "Name='$ServiceName'"
if ($service -ne $null)
#Stop the service
$status = & "sc.exe" "$ServerName" stop "$ServiceName"
"Stop status : $status"
"Deleting Service..."
$returnCode = $service.delete().ReturnValue
"Return code was : $returnCode"
if ($returnCode -ne 0)
$(throw "The deletion of the service failed: Return code was $returnCode")
#Ensure the service was deleted successfully
$service = Get-WmiObject -Class Win32_Service -Filter "Name='$ServiceName'"
if ($service -ne $null)
$(throw "The deletion of the service failed.")
else
$exitCode = 0
The above code works in all cases that I've run it for. You can either edit the existing ManageWindowsServices script, or simply create a new one. I opted for the latter.
Note: This is my first attempt at using Powershell, so there may well be a better way of doing the above.

Mounting lvm (on raid) fails every few boots

Hi,
as the title says, every few boots (probably every 5th boot or so) I get dropped to an emergency console because mounting one of my logical volumes (not always the same one) fails.
I have attached the logs form a successful and unsuccessful boot. The relevant lines I could find are:
Job dev-mapper-raidvg\x2dlvimages.device/start timed out.
Nov 01 07:58:01 mythbackend systemd[1]: Timed out waiting for device dev-mapper-raidvg\x2dlvimages.device.
Nov 01 07:58:01 mythbackend systemd[1]: Dependency failed for /home/laffi/media/images.
Nov 01 07:58:01 mythbackend systemd[1]: Dependency failed for Local File Systems.
Nov 01 07:58:01 mythbackend systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Nov 01 07:58:01 mythbackend systemd[1]: Dependency failed for File System Check on /dev/mapper/raidvg-lvimages.
Another thing I noticed is that a filesystem check gets started for that particular lv (lvimages) during the successful boot, but not the unsuccessful one. No idea if that means anything.
As you can see from the full log other lv's get mounted successful during the same boot.
The raid also seems to get started fine. I noticed this line in the logs, but it's in both the successful and unsuccessful boots so it probably is not the issue.
Nov 01 07:56:31 mythbackend systemd[1]: Cannot add dependency job for unit lvm.service, ignoring: Unit lvm.service failed to load: No such file or directory.
This is my fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
# /dev/sda1 /boot ext4 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda5 / ext4 defaults 0 1
#/dev/VolGroup01/lvolhome /home ext4 defaults 0 1
#/dev/raidvg/lvhome /home ext4 defaults 0 2
/dev/sda7 /home ext4 defaults 0 2
/dev/mapper/raidvg-lvmusic /home/laffi/media/music ext4 defaults 0 2
/dev/mapper/raidvg-lvphotos /home/laffi/media/photos ext4 defaults 0 2
/dev/mapper/raidvg-lvvideos /home/laffi/media/videos xfs defaults 0 2
/dev/mapper/raidvg-lvmovies /home/laffi/media/movies xfs defaults 0 2
/dev/mapper/raidvg-lvcamcorder /home/laffi/media/camcorder ext4 defaults 0 2
/dev/mapper/raidvg-lvrecordings /home/laffi/media/recordings xfs defaults 0 2
/dev/mapper/raidvg-lvlivetv /home/laffi/media/livetv xfs defaults 0 2
/dev/mapper/raidvg-lvrecarchive /home/laffi/media/recarchive xfs defaults 0 2
/dev/mapper/raidvg-lvbooks /home/laffi/media/books ext4 defaults 0 2
/dev/mapper/raidvg-lvimages /home/laffi/media/images ext4 defaults 0 2
# /dev/mapper/raidvg-lvbackhome /home/laffi/media/backhome ext4 defaults 0 2
/dev/sda6 /home/laffi/media/backup ext4 defaults 0 1
/dev/sdf1 /home/laffi/usbdrive ntfs defaults,nofail 0 2
Any help will be much appreciated. Thank you.u
Log of successful boot:
http://pastebin.com/raw.php?i=ZE9k76PW
Log of unsuccessful boot
http://pastebin.com/raw.php?i=12FH8S1B

WonderWoofy wrote:If you vgchange -ay when it drops you into the initramfs shell, can you then exit out and continue the boot?
Ok, finally managed to try this.
vgchange -ay results in a "volume group with 11 logical volumes now active" or something along those line.
I then pressed CTRL+D to exit the emergency console. After that, nothing happened. Waited a few minutes, just in case, then rebooted (via ctrl+alt+del).
Something maybe worth noting: in the meantime I had enabled the lvm-monitoring service to see if that makes a difference (seems like it doesn't, since I still have the same problem). I found the following line(s) in this unsuccessful boot (with lvm-monitoring service enabled):
Nov 07 09:00:29 mythbackend lvm[164]: 11 logical volume(s) in volume group "raidvg" monitored
Nov 07 09:00:29 mythbackend systemd[1]: Started Load/Save Random Seed.
Nov 07 09:00:29 mythbackend systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
And then further down the following familiar lines:
Nov 07 09:00:32 mythbackend systemd[1]: Starting File System Check on /dev/sda7...
Nov 07 09:00:32 mythbackend systemd-fsck[305]: /dev/sda7: clean, 57416/640848 files, 1091272/2559488 blocks
Nov 07 09:00:32 mythbackend systemd[1]: Started File System Check on /dev/sda7.
Nov 07 09:00:32 mythbackend systemd[1]: Mounting /home...
Nov 07 09:00:32 mythbackend systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway.
Nov 07 09:00:32 mythbackend kernel: EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
Nov 07 09:00:32 mythbackend systemd[1]: Mounted /home.
Nov 07 09:00:32 mythbackend systemd[1]: Mounting /home/laffi/media/backup...
Nov 07 09:00:32 mythbackend kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Nov 07 09:00:32 mythbackend systemd[1]: Mounted /home/laffi/media/backup.
Nov 07 09:01:57 mythbackend systemd[1]: Job dev-mapper-raidvg\x2dlvrecarchive.device/start timed out.
Nov 07 09:01:57 mythbackend systemd[1]: Timed out waiting for device dev-mapper-raidvg\x2dlvrecarchive.device.
Nov 07 09:01:57 mythbackend systemd[1]: Dependency failed for /home/laffi/media/recarchive.
Nov 07 09:01:57 mythbackend systemd[1]: Dependency failed for Local File Systems.
Nov 07 09:01:57 mythbackend systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Nov 07 09:01:57 mythbackend systemd[1]: Dependency failed for File System Check on /dev/mapper/raidvg-lvrecarchive.
Any thoughts ? Thank you very much.
Last edited by dafrizz (2013-11-07 06:45:09)

GS70 2QE - Every other boot fails

Hello all
I have an issue with my Notebook. Whenever i want to boot up my Notebook, the first boot will always fail:
Notebook emits a short "beep", keyboard flashes red then shuts off. Screen stays black.
However the Notebook then automatically tries to boot again, but this time it will succeed.
Now the problem was not from the beginning on. It occured the first time around 2 months ago. But I never updated anything manually, just Windows Update and the Nvidia Graphics update (automatically).
After encountering this problem the first few times, I decided to update all that i could find on the MSI Support page to my Notebook model.
However I was not able to do a BIOS update, since the UEFI flash mode is triggered in the BIOS menu after a reboot - now, you can imagine, i am never able to enter the UEFI flashmode because the first boot that should enter the UEFI flasmode will fail. The next successfull boot somehow will not remember that it should enter the UEFI flashmode....
I appreciate any help!
Thanks

So I just flashed the newest BIOS with the flashtool you provided. It succeeded in flashing!
Yet, as you stated before, the problem still occurs.
thank you so far for your support though
I have found another user having the exact same issue as I have in this topic.
But there wasn't a solution either
next thing would probably be a factory reset (F3 on bootup)? Even though I'm pretty sure it wont help either, it feels like it is a hardware issue now.
Or do u happen to have another idea?

Filter to convert HTTP request to JNLP arguments fails every other time

I want to pass HTTP request parameters to a Java Web Start program as arguments. I have implemented a filter which adds the arguments from the request parameters using XML DOM, and I also set the Last-Modified date to the current date/time. [ I am sort of thinking I should put the date as the file date -- not sure ]
The filter works successfully ever other time I invoke a given URL. If I switch parameters, it looks like the filter works every time.
When the filter works, there are HTTP GET and HEAD requests. When the filter fails, there are three HEAD requests and one GET request. Using the apache soap TCP Tunnel/Monitor, it looks like the HTTP request parameters aren't being passed for the second GET.

Varad and Sc0tt,
Thank you both for your responses.
Varad – Yes, I can/will reduce the amount of data so it does not cause the tabular form to go over the 2000 field limit. If that is not possible, I will at least make the users aware of this issue. Since the same data is used for the other pages in the application, the users might want to keep all the data.
Sc0tt – thanks for providing the information for your environment and settings. To plan for the future, we will have to set the value to something high also, around 8-10K range, and adjust later if we have to.
Thank you both, I will mark both of your answers as helpful and the question as being answered.
DP
(Have either of you used the jquery datepicker solution? If yes, can you please take a look at my thread: Thread: Jquery Datepicker calendar problem with page scrolling
Jquery Datepicker calendar problem with page scrolling

Weblogic 10.3 Bridge fails every other message

We have setup a bridge between to Tibco EMS servers. The source and target destinations are setup as eis.jms.WLSConnectionFactoryJNDIXA adapters. Start-up the bridge connects to both destinations without problems, so far so good. Once a message appears in the source queue it is able to forward one message and then fails. The bridge attempts to reconnect but fails repeatedly. Also, we noted that we have a transaction that is in committing state for hours. But we can't find this transaction on the tibco server. If you try ot rollback the transaction from the weblogic console it informs you that the object has been deleted.
"The object that you were viewing has been deleted, either by you or another user. Please make another selection. "
Also, here is the error we see in the logs:
<Nov 4, 2010 3:33:49 PM CET> <Warning> <JTA> <BEA-110484> <The JTA health state has changed from HEALTH_OK to HEALTH_WARN with reason codes: Resource eis/jms/WLSConnectionFactoryJNDIXA declared unhealthy.>
<Nov 4, 2010 3:33:49 PM CET> <Warning> <JTA> <BEA-110204> <XA resource [eis/jms/WLSConnectionFactoryJNDIXA] returns XAER_RMFAIL and is unavailable.>
<Nov 4, 2010 3:33:49 PM CET> <Error> <MessagingBridge> <BEA-200015> <An error occurred in bridge "TS-Bridge-CSAR" during the transfer of messages (java.lang.Exception: javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA_branchalias_3': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException
     at com.tibco.tibjms.TibjmsXAResource.startTx(TibjmsXAResource.java:533)
     at com.tibco.tibjms.TibjmsXAResource.start(TibjmsXAResource.java:229)
     at weblogic.connector.security.layer.AdapterLayer.start(AdapterLayer.java:513)
     at weblogic.connector.transaction.outbound.XAWrapper.start(XAWrapper.java:466)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1183)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1116)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
     at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:113)
     at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
     at $Proxy61.createMessage(Unknown Source)
     at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1455)
     at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
     at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
     at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:201)
     at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
     at $Proxy61.createMessage(Unknown Source)
     at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1455)
     at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
     at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA_branchalias_3': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException
     at com.tibco.tibjms.TibjmsXAResource.startTx(TibjmsXAResource.java:533)
     at com.tibco.tibjms.TibjmsXAResource.start(TibjmsXAResource.java:229)
     at weblogic.connector.security.layer.AdapterLayer.start(AdapterLayer.java:513)
     at weblogic.connector.transaction.outbound.XAWrapper.start(XAWrapper.java:466)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1183)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1116)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
     at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:113)
     at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
     at $Proxy61.createMessage(Unknown Source)
     at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1455)
     at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
     at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1140)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
     at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:113)
     ... 8 more
).>
<Nov 4, 2010 3:33:49 PM CET> <Warning> <JTA> <BEA-110405> <Resource eis/jms/WLSConnectionFactoryJNDIXA was not assigned to any of these servers: Core1 >
Any idea what may be the problem.? We have about 10 bridges only 3 are failing. The three that are failing are bridging between the same servers.
Edited by: 807664 on Nov 5, 2010 12:08 AM

Thanks for the feedback atheek1.
We already have this patch: CR364493_103.jar. We have added this jar to the classpath of our servers start-up (not the admin server but our application server only) script and it still fails. We also turned on debug level logging for the bridges but we can't see why the connection failed. What we do see is a huge number of "Connections Destroyed by Error" in the jmx-xa-adp monitor page total count from the past 3 days is 100666. The current connections are 20 and we have 58 Reject Connections. Also, once a message is sent and fails then the transaction is rolled back but it never finishes to rollback. The transaction is stuck for many hour looks like close to 24 hours and then it sometimes disappears at this point the bridge tries to resend and sometime it succeeds and sometimes it fails.
We are running out of options, if we can't fix this soon then we will have to use another solution for our bridging, maybe roll our own.

H67MA-E35 (B3) - Freeze during every other boot with USB IR receiver plugged in.

Hi, I have an HTPC with an MSI H67MA-E35 (B3) motherboard. I also have a Hama VRC-1100 remote (Microsoft Media Center compatible), which has its own USB infrared receiver. When it's plugged in and I turn on the PC, it won't boot. It gets to the Windows boot screen and freezes before the logo itself starts to form. I have to do a hard reset, then it boots fine. If I reboot the PC, I get the same problem and have to hard reset again.
The IR receiver has the latest drivers and I've tried plugging it into different ports to no avail. I've also tried changing the BIOS settings to resume using OS instead of the BIOS, but then the remote cannot wake the PC up.

Apologies, the MSI Live Update tool says I have an MS-7680 motherboard with a B.90 BIOS. A scan for updates shows no new BIOS versions. Here are the rest of my specs:
Intel Celeron G530 (Sandy Bridge S1155)
MSI H67MA-E35 (B3)
4 GB of Kingston DDR3 1333 MHz RAM (2 sticks, running at 1066 MHz)
nVidia GT 430 with 1 GB VRAM (Asus ENGT430 DC SL/DI/1GD3, fanless)
40 GB Intel 320 Series SSD
Western Digital Green 1.5 TB HDD (WD15EARS)
Samsung BD-RE (SH-B123L/BSBP)
Antec EarthWatts EA-380D PSU
BlackGold DVB-S2/T2 Tuner (BGT3630)
Windows 7 Professional x64

Why does the 3g data network fail every day?

Goes down for at least an hour a day

Is this in a highly populated area? Is it the same location and time usually?

TS1398 i can access my wireless network on every other device EXCEPT my new iPad - any thoughts on why?

any idea about what's going on and why i can't connect my wireless account to the the "new iPad?"

Yup that would have worked.

Native application installer fails on Mac 10.5.8 every other time

Hello,
I have a native AIR 2.0 application with a native installer which I silently install as a part of a bigger package.
On Mac, I have a DMG which contains the native installer app and a shell script which copies the native installer app into a temporary folder, and then invokes it passing "-silent" option.
For some reasons the native installer fails every other time, i.e. if I install the app and then move it to trash and then try to re-install, the installer fails.
However if I try re-installing once again, installation succeeds. I can consistently reproduce this problem.
This seems to happen only on Mac OS 10.5.8. On 10.6.0 and above everything seems to work fine.
What can be the reason for such inconsistent behavior?
OS version is Mac OS 10.5.8, CPU: 2.8GHz Intel Core Duo
Below is the log for the cases when the installer fails:
Nov 10 20:19:08 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[9579]: Application signature verified
Nov 10 20:19:08 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[9579]: Unpackaging/validation complete
Nov 10 20:19:08 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[9579]: Got an unexpected fatal error while unpackaging: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Unhandled exception ArgumentError: Error #2004" errorID=2004]
Nov 10 20:19:08 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[9579]: Application Installer end with exit code 7
Thanks in advance

Chris, thank you for your answer.
The only argument I pass into the installer command line is "-silent", i.e. the command line looks like
"/tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline" -silent
I've noticed that the installer fails only if it's called from a wrapper package. If I invoke the above command line directly from Terminal, the installer consistently succeeds.
Here is the full log for the case when installer fails:
Nov 15 11:21:21 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37088]: Bootstrapper begin (Mac:version (null))
Nov 15 11:21:21 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37088]: Installed runtime located (2.5.0.16600)
Nov 15 11:21:21 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37088]: Launching application installer: "AIR Application Installer" -silent /tmp/PixelNovel/Install Timeline.app/Contents/Resources/Timeline
Nov 15 11:21:21 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37089]: Application Installer begin with version 2.5.0.16600 on Mac OS 10.5.8 x86
Nov 15 11:21:21 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37089]: Commandline is: -silent "/tmp/PixelNovel/Install Timeline.app/Contents/Resources/Timeline"
Nov 15 11:21:21 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37089]: Installed runtime (2.5.0.16600) located at /Library/Frameworks/Adobe AIR.framework
Nov 15 11:21:22 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37089]: Validating app in folder /tmp/PixelNovel/Install Timeline.app/Contents/Resources/Timeline/Contents/Resources
Nov 15 11:21:23 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37089]: Application signature verified
Nov 15 11:21:23 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37089]: Unpackaging/validation complete
Nov 15 11:21:23 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37089]: Got an unexpected fatal error while unpackaging: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Unhandled exception ArgumentError: Error #2004" errorID=2004]
Nov 15 11:21:23 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37089]: Application Installer end with exit code 7
Nov 15 11:21:23 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37088]: Application installer failure (7)
Nov 15 11:21:23 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37088]: Bootstrapper failure (7)^M
And here is the log for a successful attempt:
Nov 15 11:25:19 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37154]: Bootstrapper begin (Mac:version (null))
Nov 15 11:25:19 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37154]: Installed runtime located (2.5.0.16600)
Nov 15 11:25:19 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37154]: Launching application installer: "AIR Application Installer" -silent /tmp/PixelNovel/Install Timeline.app/Contents/Resources/Timeline
Nov 15 11:25:20 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Application Installer begin with version 2.5.0.16600 on Mac OS 10.5.8 x86
Nov 15 11:25:20 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Commandline is: -silent "/tmp/PixelNovel/Install Timeline.app/Contents/Resources/Timeline"
Nov 15 11:25:20 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Installed runtime (2.5.0.16600) located at /Library/Frameworks/Adobe AIR.framework
Nov 15 11:25:20 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Validating app in folder /tmp/PixelNovel/Install Timeline.app/Contents/Resources/Timeline/Contents/Resources
Nov 15 11:25:21 iMac-3 /usr/sbin/ocspd[37158]: starting
Nov 15 11:25:21 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Application signature verified
Nov 15 11:25:21 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Unpackaging/validation complete
Nov 15 11:25:21 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: No app located for appID 'com.pixelnovel.TimelineProjectManager' and pubID ''
Nov 15 11:25:21 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Starting silent app installation to /Applications. Installing app com.pixelnovel.TimelineProjectManager version 0.0.4 using the source file at file:///tmp/PixelNovel/Install%20Timeline.app/Contents/Resources/Timeline
Nov 15 11:25:22 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Launching subprocess with commandline /usr/sbin/chown -hfRP root:wheel /Applications/Timeline.app
Nov 15 11:25:22 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Subprocess chown succeeded
Nov 15 11:25:22 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Launching subprocess with commandline /bin/chmod -R ugo+rx /Applications/Timeline.app
Nov 15 11:25:22 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Subprocess chmod succeeded
Nov 15 11:25:22 iMac-3 /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR Application Installer.app/Contents/MacOS/Adobe AIR Application Installer[37155]: Application Installer end with exit code 0
Nov 15 11:25:22 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37154]: Application installer success
Nov 15 11:25:22 iMac-3 /tmp/PixelNovel/Install Timeline.app/Contents/MacOS/Install Timeline[37154]: Bootstrapper success^M
I will also send you a link to the DMG file that reproduces the error as a private message - ma be this will help.
Thank you,
Anatoly

Network fails every other boot [SOLVED]

Similar Messages

Maybe you are looking for