Syslog error - WAAS-SYS-3-900000: e1000bp: eth5: e1000bp_clean_tx_irq: Detected Tx Unit Hang

I am receiving this error in my syslog, every couple weeks or so. It causes a flap between our two inline WAEs. Have an idea what can be causing this? syslog is below, start from the bottom up.
2011-03-10 10:30:08 Kernel Error 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-3-900000: e1000bp: eth4: e1000bp_watchdog: NIC Link is Up 1000 Mbps Full Duplex
2011-03-10 10:30:06 Kernel Error 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-3-900000: e1000bp: eth5: e1000bp_watchdog: NIC Link is Up 1000 Mbps Full Duplex
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: next_to_watch.status <0>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: jiffies <2b900a9e1>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: next_to_watch <91>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: time_stamp <2b9008c71>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: buffer_info[next_to_clean]
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: next_to_clean <91>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: next_to_use <7e>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: TDT <7e>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: TDH <91>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: Tx Queue <0>
2011-03-10 10:30:02 Kernel Error 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-3-900000: e1000bp: eth5: e1000bp_clean_tx_irq: Detected Tx Unit Hang

Here is the output from the show alarms hist, also there are no visual LED problem with the device.
     Op Sev Alarm ID             Module/Submodule     Instance
   1 C Mi servicedead          nodemgr              cms_ce
     Mar 7 15:00:41.435 EST, Processing Error Alarm, #000008, 2000:330004
     nodemgr: The cms_ce service died.
   2 R Mi servicedead          nodemgr              cms_ce
     Mar 7 15:00:31.233 EST, Processing Error Alarm, #000008, 2000:330004
     nodemgr: The cms_ce service died.
   3 C Mi servicedead          nodemgr              device_mgr
     Feb 2 11:31:45.484 EST, Processing Error Alarm, #000007, 2000:330004
     nodemgr: The device_mgr service died.
   4 R Mi servicedead          nodemgr              device_mgr
     Feb 2 11:31:35.282 EST, Processing Error Alarm, #000007, 2000:330004
     nodemgr: The device_mgr service died.
   5 C Mi servicedead          nodemgr              device_mgr
     Jan 22 20:39:47.480 EST, Processing Error Alarm, #000006, 2000:330004
     nodemgr: The device_mgr service died.
   6 R Mi servicedead          nodemgr              device_mgr
     Jan 22 20:39:37.276 EST, Processing Error Alarm, #000006, 2000:330004
     nodemgr: The device_mgr service died.

Similar Messages

Waas error message - WAAS-SYS-4-900000: time.c: can't update CMOS

This was moved from another board,
I this error on our syslog server from our WAE-7371 (running older code, but that is in the works to upgrade shortly,4.1.3b) , and I have checked the clocks on the inline devices and the CM and all are set insync. Any other ideas?
kernel: %WAAS-SYS-4-900000: time.c: can't update CMOS

Hi Cora,
With the NTP source being the same on on all devices and the clock in sync among them, the battery problem was confirmed in the bmc.log as the last entries indicated the power off/down with timestamp 01/02/1970.
The resolution is to RMA the appliance.
Regards,
Fabio Bergamo
Cisco TAC

WAAS hardware is OE612, but Rescue Disk detects model as OE512

I've had this issue with 2 RMA'd OE612s already. They originally shipped with 4.0.19, which worked fine, but failed on upgrade to 4.2.1.
Recovery attempt #1 with 4.0.19 Rescue disk displayed :
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
   MODEL: UNKNOWN
   FLASH: found, directory validated
COOKIE: invalid
   IMAGE: NONE
FLASHDEV: /dev/hda
Installer Main Menu:
    1. Configure Network
    2. Manufacture flash
    3. Install flash cookie
    4. Install flash image from network
    5. Install flash image from cdrom
    6. Install flash image from disk
    7. Wipe out disks and install .bin image
    8. Exit (and reboot)
Choice [0]: 3
Unknown model, cannot create cookie.
Subsequent Recovery procedures using Rescue disks from 4.1.7 and 4.2.1 detected the Model as OE512. Option 2 creates a cookie as a MODEL OE512, which I wrote with option 3. Option 5 works, but trying to write the bin image on 4.1.7 displays this
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Choice [0]: 8
Enter full URL of .bin image to install.
   ftp://[user:pass@]ip_addr/path/to/file
http://[user:pass@]ip_addr/path/to/file
file:/local/path/to/to/file
URL for .bin image [file:/cdrom/images/WAAS41.bin]:
Continue? This will wipe out all disks! [n]: y
Scrogging done
Saving random seed...
dd: opening `/state/random-seed': No such file or directory
No volume groups found
/ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdown, or it has unknown data.
/ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
/ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdown, or it has unknown data.
/ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: op_open or media_open
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: op_create or media_init
SSMGR RETURNING: 10 (No such file or directory)
Reading and installing image, it may take a few minutes, please wait...
Error, image NOT installed.
   MODEL: OE512
   FLASH: found, directory validated
COOKIE: valid
   IMAGE: 4.1.7.11
FLASHDEV: /dev/sda
Installer Main Menu:
    1. Configure Network (done)
I suspect that the Installer program on the Rescue CD can't detect the Hardware properly, and thus can't find the proper drivers for the platform.
Is there any manual method of forcing the Rescue CD Installer to use a particular hardware model?
Thanks,
Tom

Hi Zach,
>What led you to change the Adaptec configuration?
I was directed to do so by TAC, although I wasn't sure why, since our other WAE-612-k9s didn't have this option enabled.
>What is the state of the device prior to upgrading? Does the WAAS software boot?
After disabling the hardware raid, the WAE could run any 4.0.x version, but could not upgrade to 4.1/4.2. I tried both the "rescue CDs" for 4.1/4.2, and the "copy ftp install" methods. "Rescue CDs" would work right up to the option for "wipe disks and install .bin" image, but would report "no disks" as shown above. The "copy ftp install" from version 4.0.27 would install the 4.2.1.38 image, but upon reboot, it would fail during the boot sequence
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Frustrated, I looked at the boot logs and might have found an issue. On the "faulty" WAE-612, the boot script detects two SCSI adapters; only one shows up in BIOS POST.
The first adapter (Adaptec AIC79XX) has no drives, but is assigned the device name "scsi0"
Under the second adapter(Adaptec AIC94XX), the Hard disks are detected, and it's assigned a device name of "scsi1"
ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 17 (level, low) -> IRQ 17
scsi0 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 2.0.30
        aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs
Adaptec aacraid driver 1.1-5[24495]custom-IBM
Loading AIC-94xx Linux SAS/SATA Family Driver, Rev: 1.0.8-12
Probing Adaptec AIC-94xx Controller(s)...
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 19 (level, low) -> IRQ 19
scsi1 : Adaptec AIC-9405W SAS/SATA Host Adapter
scsi 1:0:128:0: Direct-Access     IBM-ESXS ST3146755SS      BA33 PQ: 0 ANSI: 5
adp94xx:0:128:0: Tagged Queuing enabled. Depth 32
scsi 1:1:128:0: Direct-Access     IBM-ESXS ST3146755SS      BA33 PQ: 0 ANSI: 5
adp94xx:1:128:0: Tagged Queuing enabled. Depth 32
AIC-94xx controller(s) attached = 1.
To contrast, our functioning WAE-612s do not have this second detected Adaptec host adapter, and are properly assigned a "scsi0" for their device name.
Adaptec aacraid driver 1.1-5[24495]custom-IBM
Loading AIC-94xx Linux SAS/SATA Family Driver, Rev: 1.0.8-12
Probing Adaptec AIC-94xx Controller(s)...
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 19 (level, low) -> IRQ 19
scsi0 : Adaptec AIC-9405W SAS/SATA Host Adapter
scsi 0:0:128:0: Direct-Access     IBM-ESXS MBA3300RC        SA06 PQ: 0 ANSI: 5
adp94xx:0:128:0: Tagged Queuing enabled. Depth 32
scsi 0:1:128:0: Direct-Access     IBM-ESXS MBA3300RC        SA06 PQ: 0 ANSI: 5
adp94xx:1:128:0: Tagged Queuing enabled. Depth 32
AIC-94xx controller(s) attached = 1.
On our faulty WAE-612, in the section that tries to mount the detected drives, it appears that the script is looking for the physical drives under the "scsi0" device name, using the AIC94XX driver.. .
2010 Jul 8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi disk sda a
t scsi1, channel 0, id 128, lun 0
2010 Jul 8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi disk sdb a
t scsi1, channel 1, id 128, lun 0
2010 Jul 8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi removable
disk sdc at scsi2, channel 0, id 0, lun 0
BOOT-100: disk apply
scan_612_disk_map: Can't open . Errno=2
change_disknum_612 failed!
/ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdo
wn, or it has unknown data.
/ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
I'm guessing this fails because there are no physical drives on "scsi0", they are assigned on "scsi1". If the disk mapping script would've tried , I think the drives would've been mounted properly.
I was hoping there was a modified script out there somewhere, but after our 3rd RMA'd WAE exhibited the same characteristics (these were all in Chennai India), I directed the onsite tech to remove the Adaptec 29320ALP UltrasSCSI adapter.
With the adapter removed, the 4.2.1.38 code installed and booted properly.
When I forwarded my results to TAC, our Rep mentioned that the WAE-612-k9 ships with both ACNS and WAE capabilities. He said that ACNS uses that additonal SCSI card.
I'm fairly sure our configuration is not unique; our environment consists of 32 WAEs, and this is the first time that I've encountered this issue.
I'm just happy it's resolved now.
Thanks for your insight, Zach
Tom

Error while installing Grid Control 12c (ERROR STREAM: *sys-package-mgr*: skipping bad jar)

Hi all,
   OS: OEL 6.3 64 bits
   DB: 11.2.0.3
   Grid: 12.1
   While installing Grid Control 12c, the following error appears to me:
INFO: SaveInvWCCE JRE files in Scratch
INFO: oracle.installer.mandatorySetup property is set to false, so skipping the execution of additional tools
INFO: oracle.installer.installUpdates property is set to false, so skipping the checking of updates
INFO: Config Initialize JRE files in Scratch
INFO: no env vars set, no envVars.properties file is generated
INFO: none of the components are configurable
INFO: This is a shared oracle home or remote nodes are null. No copy required.
INFO: Adding iterator oracle.sysman.oii.oiif.oiifw.OiifwRootShWCDE
INFO: Updating the global context
INFO: Path To 'globalcontext.xml' = /gridControl/WLS/jdk16/install/chainedInstall/globalcontext
INFO: Since operation was successful, move the current OiicAPISessionDetails to installed list
INFO: Install Finished at: 2013-07-04_11-12-49-PM
INFO: The ARU ID found in shiphomeproperties.xml file is 226
INFO: ARUId present in shiphomeproperties.xml matches with the 64 bit OMS Platforms ARU ID 226, so -d64 is passed for wls install.
INFO: Executing the command /gridControl/WLS/jdk16/jdk/bin/java   -d64 -Djava.io.tmpdir=/gridControl/WLS/.wlsinstall_temp -Xms128m -Xmx1024m -jar /u01/binaries//wls/wls1035_generic.jar -mode=silent -silent_xml=/gridControl/WLS/.wlsinstall_temp/wls.xml -log=/u01/oraInventory/logs/installActions2013-07-04_11-07-45PM.log.wls -log_priority=debug
INFO: Extracting 0%....................................................................................................100%
INFO: ERROR STREAM: *sys-package-mgr*: skipping bad jar, '/u01/binaries/wls/wls1035_generic.jar'
INFO: #
INFO: # A fatal error has been detected by the Java Runtime Environment:
INFO: #
INFO: # SIGSEGV (0xb) at pc=0x0000003a23689cdc, pid=24834, tid=139710737405696
INFO: #
INFO: # JRE version: 6.0_24-b50
INFO: # Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode linux-amd64 compressed oops)
INFO: # Problematic frame:
INFO: # C [libc.so.6+0x89cdc]
INFO: #
INFO: # An error report file with more information is saved as:
INFO: # /tmp/hs_err_pid24834.log
INFO: #
INFO: # If you would like to submit a bug report, please visit:
INFO: #   http://java.sun.com/webapps/bugreport/crash.jsp
INFO: #
INFO: Return value is 134
INFO: POPUP ERROR:Installation of Oracle WebLogic Server has failed, check log files for more details.
   The line "skipping bad jar, '/u01/binaries/wls/wls1035_generic.jar'" is the one that's worring me. Can it be corrupt? Or it is something else?
   Thanks in advance.

Its too early to conclude the issue is a bug with out looking into the logs. For the same reason i requested you to open an SR so that we can have a look at the logs and identify the cause. If you are Oracle employee then you can share the VM details else we need logs to debug this further. If any one from your company can open an sr and share logs then that will be helpful. Can you also check if the shiphome that you downloaded is all correct and checksum/byte matches to what is mentioned on OTN.

I just put itunes upeate 11 on and now itunes will not run. I get an error that sys iTunes has stopped and windows is sutting it down. I reinstalled 10.7 and it will not run eather now.

I just put itunes upeate 11 on and now itunes will not run. I get an error that sys iTunes has stopped and windows is sutting it down. I reinstalled 10.7 and it will not run eather now.

C Mawle wrote:
Thanks. I have followed all the instructions as recommended and nothing has worked so it looks like the restore/update may have been interrupted - would loss of internet connection do this?
Yes it would, possibly even brick it.
Have successfully connected my ipod nano with iTunes so looks like the device driver is working.
Can I use my ipod nano USB connector to check?
It is not much help to you, since the device that you need still not recognized.
Anyway looks like I may have to swallow the loss of data. Have set-up a call for tomorrow with Apple support so will wait until after this before doing the factory restore!
Good luck, but if you expect miracle from that call good luck again.

CREATE ERROR RPE-02005: Internal error: Attribute SYS:KEY

Has anyone experienced this error when deploying a WF and an idea what can cause this:
ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "OWF_MGR.WF_LOAD", line 2138
ORA-06512: at line 1
EDW_DMSA
Create
Error
RPE-02005: Internal error: Attribute SYS:KEY for Process Activity MAP_TMP_DRAMEX_QUANTITIES cannot be created or updated with SYS:KEY value A02. Please try again. If the problem persists then please contact Oracle Support with the stack trace and details on how to reproduce it.
Thanks much

The problem is the sequence cache when cloning a database as was the case here.
The cache is purged resulting in an invalid "last_cached_value".
The seq has to be manually incremented until it "pulls" a value 1 above.
The same problem was the case with a few sequences in the owbsys schema as well.
Having done this execise I could deploy all my WF.

WLC Syslog error message

Hi all,
I get a lot of the following syslog error messages from 3 of my 4 WLCs (two WiSMs).
Error message:
ethoip.c:342 ETHOIP-3-PKT_RECV_ERROR
I searched at cisco.com and I found the information to use the bug toolkit or open a tac case, but I didn't find a bug or any further information related to that problem.
I can not even recognize any differences in the WLC configs - for centralize configuration I use an WCS.
WiSM Software version: 5.0.148.0
WCS Software vesion: 5.0.56.0
Does anyone of you had the same problem?
Thank you for all information!
Best regards
Peter

Hi dennischolmes,
after your post I checked the mobility group configuration on all four controllers, and indeed, there was a inconsitency in the configuration. The WCS couldn't see the mismatch, because the settings between the WCS and the controllers were the same. As I looked on the controllers web pages i saw, that different mobility group memebers with various mobility group names were configured on every single controller, maybe caused by applying a new controller template, where i changed the mobility group name.
I started from scratch configuring the mobility groups and the syslog error messages were stopping.
Thank you very much!

Hard reset problem and error message (sys 0505) (0, 841) Palm T/X

I've read the various posts covering the error message and I believe I downloaded an incompatible program using the Addit site. While attempting to do a hard reset (following the user guide) I am unable to reach the screen showing the reset options. I receive the error message (sys 0505) (0, 841) in a box in front of the preferences screen after the palm resets (soft). There is a Software icon that was placed on my opening page on the Palm, which when pressed shows the same error message. Any suggestions on how to remove the program or reset the Palm T/X would be helpful.Thanks.
Post relates to: Palm TX

The error is caused by the installation of MyPalm, MyTreo, or MyHand on your device. These were designed for phones.
Delete any of the ones mentioned and the problem should go away.
Your timing may be a bit off when trying to do the Hard Reset.
To perform a Hard Reset: (Palm Knowledgebase article #887)
While pressing and holding the Power button down, tap and release the Reset button in back and continue to hold the Power button down. When the grey Palm logo appears, you can release the Power button.
You should now see the warning page in about 5 languages. Press the UP direction on the 5-way pad to complete the task. Your Palm will reset itself several times as it re-installs the original programs and erases all your previous data.
WyreNut
Post relates to: Centro (AT&T)
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

Error Message (Sys 0505) (0,841)

Hi
Does anyone know what an error Message (Sys 0505) (0,841) is and how to get rid of it?
Thanks
Post relates to: Palm TX
This question was solved.
View Solution.

There have been several threads on that error message. Does anything here help?
Hard reset problem and error message (sys 0505) (0, 841) Palm T/X [Dec.2008]
http://forums.palm.com/palm/board/message?board.id=software&thread.id=34723
Palm TX error message (sys 0505) (0,841) PLEASE HELP![Feb.2008]
http://forums.palm.com/palm/board/message?board.id=hardware&thread.id=26465
Error (Sys 0505)(0841)[Nov.2007+]
http://forums.palm.com/palm/board/message?board.id=windows_hotsync&thread.id=26479
error(Sys 0505) (0, 841) [May 2007+]
http://forums.palm.com/palm/board/message?board.id=software&thread.id=13924
Post relates to: Treo 800w (Sprint)

[SOLVED]systemd-fstab-generator and syslog error?

here is the bootup error message:
Nov 2 07:27:58 localhost [ 9.207762] systemd-fstab-generator[151]: Failed to create unit file: File exists
Nov 2 07:27:58 localhost [ 10.119699] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
Nov 2 07:27:58 localhost [ 10.544789] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 07:27:58 localhost [ 10.544974] systemd[1]: Failed to listen on Syslog Socket.
and my fstab is here:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb5 / jfs defaults 0 1
/dev/sdb6 /home ext4 defaults,user_xattr 0 1
/dev/sdb7 /var reiserfs defaults 0 1
/dev/sdb8 /tmp reiserfs defaults 0 1
Last edited by frat (2012-11-02 03:21:07)

systemd-fstab-generator is fixed,thank you.
syslog errors still:
Nov 2 10:29:44 localhost [ 10.051816] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 10:29:44 localhost [ 10.052000] systemd[1]: Failed to listen on Syslog Socket.
#systemctl status syslog
syslog.service
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)
#systemctl status syslog.socket
syslog.socket - Syslog Socket
   Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static)
   Active: inactive (dead)
   Docs: man:systemd.special(7)
   http://www.freedesktop.org/wiki/Software/systemd/syslog
   CGroup: name=systemd:/system/syslog.socket
any advice?
Last edited by frat (2012-11-02 02:56:37)

ITunes unable to recognize iPod, error message along the lines if "iTunes has detected an iPod but unable to recognise" I have followed all the trouble shooting tips and am still stuck? I am now being told by a friend I need a link sent to me to fix this

Hi,
I am need of help! I have had this issue for a while now and it's becoming frustrating.
My iTunes installed on my HP Windows 8 Netbook is unable to recognize my iPod, the error message along the lines of "iTunes has detected an iPod but unable to recognise"
I have followed all the trouble shooting tips and am still stuck? I am now being told by a friend I need a link sent to me to fix this??
Someone please help me fix this problem.
Many thanks.
Matt.

Hi
So just close iTunes and re-open iTunes thats it and that worked for you?
When you say reset your settings do you mean to factory settings? As my iPod was swapped at the store for a new one and the problem is still there...
Thanks.

Getting an error in KPI Modeler as "{"customMessage":"failed to detect the sap language of the current session language","status":500}"

Hi Experts,
We have installed UISKPI01 in SAP NetWeaver Gateway System for Fiori Analytical Apps (KPI modeler is necessary to model the KPI) but while trying to create and Save the Group, we are Getting an error in KPI Modeler as "{"customMessage":"failed to detect the sap language of the current session language","status":500}". Similarly, when we are trying to edit the existing KPI template and assigning the Variants and Evaluations, we are facing the same error as failed to detect the sap language of the current session language","status":500.
Any idea on above error?
Thanking you,
~ Mahendra

Hello Mahendra,
Check if you have entries in the T002 table of SAP_SSB schema.
If not follow the steps mentioned in the admin guide of SAP Smart business to populate data.
This should resolve this issue.
Note: My assumption is that, you are accessing the KPI modeler in English Language.
Thanks,
Debasish

Using Adobe 11 reader, now comes up with an error, once file is opened. 'Invalid plugin detected, Adobe reader will quit. Closes the program so cannot view PDF files. Running windows 7. I have uninstalled and re-installed Adobe still the same. HELP

Using Adobe 11 reader, now comes up with an error, once file is opened. 'Invalid plugin detected, Adobe reader will quit. Closes the program so cannot view PDF files. Running windows 7. I have uninstalled and re-installed Adobe still the same. HELP

Sounds like something has been added into the Reader folder. I would recommend uninstalling, running http://labs.adobe.com/downloads/acrobatcleaner.html, removing any left over parts of the Reader folder (this might have been the problem), reboot, and reinstall. Hopefully that solves the problem. For future question about Reader, you should consider asking in the Reader forum, this is not it.

Internal error 10014, 7686536,7686826, 10069773. FrameMaker has detected a serious problem and must

Hi,
I am getting the below error whenever I try to run the extend script. Please let me know how to solve the issue.
"Internal error 10014, 7686536,7686826, 10069773. FrameMaker has detected a serious problem and must quit.
A file named "C:\Documents and Settings\valee\Application Data\Adobe\FrameMaker\10\FrameLog_11.07.28_15.41.01.txt" has been generated which contains information that may help Frame development improve the product for future releases."
Review the file content here:
=== Header Begin ===
Internal Error: 10014, 7686536, 7686826, 10069773
FrameMaker 10.0.1 for Intel
Build: 10.0.1.402
Window System: MSWindows
Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)
Generated on: Thursday, July 28, 2011 3:41:01 PM
To file: C:\Documents and Settings\valee\Application Data\Adobe\FrameMaker\10\FrameLog_11.07.28_15.41.01.txt
=== Header End ===
=== Stack Trace Begin ===
$754988
$754aaa
$99a70d
=== Stack Trace End ===
=== Open Window List Begin ===
# not implemented
=== Open Window List End ===
=== Recent Commands Begin ===
=== Recent Commands End ===
=== Recent API Calls Begin ===
# not implemented
=== Recent API Calls End ===
=== Windows Relocation Information Begin ===
Application: 00400000
FrameMaker.exe: 00400000 0092f000
ntdll.dll: 7c900000 000b2000
kernel32.dll: 7c800000 000f6000
FMRuntime.dll: 10000000 00042000
USER32.dll: 7e410000 00091000
GDI32.dll: 77f10000 00049000
tbb.dll: 00350000 00020000
MSVCP90.dll: 78480000 0008e000
MSVCR90.dll: 78520000 000a3000
FMGridCtrl.dll: 00370000 0002c000
mfc90u.dll: 789e0000 003a1000
SHLWAPI.dll: 77f60000 00076000
ADVAPI32.dll: 77dd0000 0009b000
RPCRT4.dll: 77e70000 00093000
Secur32.dll: 77fe0000 00011000
msvcrt.dll: 77c10000 00058000
COMCTL32.dll: 773d0000 00103000
MSIMG32.dll: 76380000 00005000
OLEAUT32.dll: 77120000 0008b000
ole32.dll: 774e0000 0013e000
Asn.er.dll: 003b0000 0003c000
OLECLI32.dll: 71e10000 00015000
MPR.dll: 71b20000 00012000
AdobePSL.dll: 00d30000 00d0d000
FMBMP2Tiff.dll: 01a40000 00006000
libtiff.dll: 01a50000 00085000
zlib1.dll: 01ae0000 00013000
MSVCP60.dll: 76080000 00065000
FMTiff2PS.dll: 01b00000 0000b000
COMDLG32.dll: 763b0000 00049000
SHELL32.dll: 7c9c0000 00817000
gdiplus.dll: 4ec50000 001ab000
USP10.dll: 74d90000 0006b000
FMDBMS32.dll: 01b10000 0000e000
oledlg.dll: 7df70000 00022000
VERSION.dll: 77c00000 00008000
WININET.dll: 3d930000 000d1000
Normaliz.dll: 01b20000 00009000
iertutil.dll: 3dfd0000 00045000
WINSPOOL.DRV: 73000000 00026000
amtlib.dll: 01b30000 000ee000
AIDE.dll: 01c30000 00064000
MSVCR80.dll: 78130000 0009b000
MSVCP80.dll: 7c420000 00087000
BIB.dll: 01cb0000 00049000
CoolType.dll: 01d10000 002fb000
SVGRE.dll: 6f130000 00332000
icuuc32.dll: 4a800000 00095000
icudt32.dll: 4ad00000 0095a000
MSVCR71.dll: 7c340000 00056000
icuin32.dll: 4a900000 000aa000
NetLib.dll: 02030000 0001e000
CoreTypes.dll: 30100000 00026000
NetIO.dll: 30900000 00018000
LIBCURL.dll: 30000000 00023000
WS2_32.dll: 71ab0000 00017000
WS2HELP.dll: 71aa0000 00008000
WINMM.dll: 76b40000 0002d000
SSLEAY32.dll: 02090000 00027000
LIBEAY32.dll: 020c0000 000d1000
WSOCK32.dll: 71ad0000 00009000
icuio32.dll: 4ab00000 0000b000
MSVCP71.dll: 7c3a0000 0007b000
AdobePDFL.dll: 021a0000 0067b000
AdobeXMP.dll: 02830000 0004c000
JP2KLib.dll: 02890000 000aa000
BIBUtils.dll: 02950000 00040000
AGM.dll: 029a0000 0059d000
AXE8SharedExpat.dll: 02f50000 0002e000
XAPToolkitRelease.dll: 02f90000 0008b000
AdobeXMPFiles.dll: 03030000 0006c000
AdobeLinguistic.dll: 030b0000 001af000
PSAPI.DLL: 76bf0000 0000b000
AdobeOwl.dll: 03270000 00156000
AdobeOwlCanvas.dll: 033e0000 00048000
LogSession.dll: 03440000 00056000
SETUPAPI.dll: 77920000 000f3000
adbeape.dll: 034b0000 00009000
ahclient.dll: 034d0000 00021000
IMM32.DLL: 76390000 0001d000
LPK.DLL: 629c0000 00009000
tbbmalloc.dll: 03a30000 0000a000
UxTheme.dll: 5ad70000 00038000
MFC90ENU.DLL: 5d360000 0000d000
rdpsnd.dll: 5dac0000 00008000
WINSTA.dll: 76360000 00010000
NETAPI32.dll: 5b860000 00055000
MSCTF.dll: 74720000 0004c000
fmres.dll: 0ad90000 0025e000
fmdlg.dll: 04c40000 00064000
fmcustom.dll: 04cb0000 0005d000
msctfime.ime: 755c0000 0002e000
amtservices.dll: 0b0f0000 00112000
IPHLPAPI.DLL: 76d60000 00019000
WINHTTP.dll: 4d4f0000 00059000
adobe_caps.dll: 0b460000 0006a000
NTMARTA.DLL: 77690000 00021000
SAMLIB.dll: 71bf0000 00013000
WLDAP32.dll: 76f60000 0002c000
asneu.dll: 0b5f0000 00028000
xpsp2res.dll: 0b840000 002c5000
CLBCATQ.DLL: 76fd0000 0007f000
COMRes.dll: 77050000 000c5000
wbemprox.dll: 74ef0000 00008000
wbemcomn.dll: 75290000 00037000
wbemsvc.dll: 74ed0000 0000e000
fastprox.dll: 75690000 00076000
NTDSAPI.dll: 767a0000 00013000
DNSAPI.dll: 76f20000 00027000
updaternotifications.dll: 0be20000 00092000
mstask.dll: 75830000 00045000
USERENV.dll: 769c0000 000b4000
owlres.dll: 0b640000 000ae000
NetIODav.dll: 30a00000 0002c000
xerces-c_2_7.dll: 12000000 0019e000
rsaenh.dll: 68000000 00036000
unidrvui.dll: 7e5a0000 000ba000
mxdwdrv.dll: 3f500000 000c0000
FontSub.dll: 69310000 00017000
ATMLIB.dll: 73c20000 0000b000
adbeapecore.dll: 0c810000 0001b000
ACE.dll: 0c940000 000fe000
dvaadameve.dll: 0d580000 00354000
boost_threads.dll: 0d8f0000 0000e000
dvacore.dll: 0d910000 0018c000
dvaui.dll: 0dab0000 00381000
OPENGL32.dll: 5ed00000 000cc000
GLU32.dll: 68b20000 00020000
DDRAW.dll: 73760000 0004b000
DCIMAN32.dll: 73bc0000 00006000
WTSAPI32.dll: 76f50000 00008000
clickprt.dll: 0bff0000 0002f000
fmmediaannot.dll: 0c020000 0004a000
frame2pdf.dll: 0e470000 00044000
mailer.dll: 0c070000 00039000
MAPI32.DLL: 61e00000 0001f000
bookerrlog.dll: 0e4c0000 0003a000
ditamaperrlog.dll: 0e500000 0003a000
pdfsize.dll: 0e540000 0003d000
fmpdfreflow.dll: 0e580000 00041000
ecm.dll: 0e5d0000 000c3000
sgen.dll: 0e6a0000 000a8000
dispatch.dll: 0e760000 000cf000
trnslate.dll: 0e850000 0022b000
Xalan-C_1_10.dll: 0eb10000 001f8000
XalanMessages_1_10.DLL: 0ea90000 00007000
GoMarkup.dll: 0ed10000 0013b000
GoCore.dll: 0ee50000 00081000
SCL.dll: 0eaa0000 00044000
xmlcss.dll: 0f040000 001f8000
docbook.dll: 0f250000 001f3000
xhtml.dll: 0f460000 001f2000
qstart.dll: 0f670000 0002f000
cnvschma.dll: 0f6a0000 00093000
u3dfilter.dll: 0f750000 00038000
rt3d.dll: 0f790000 00327000
ditafm.dll: 0fad0000 00281000
ditafm_app.dll: 0fd70000 00210000
find_references.dll: 10050000 000a2000
PDFCommentsImport.dll: 10100000 00078000
InitCharMap.dll: 0ffa0000 00031000
PreserveEntity.dll: 10180000 001ed000
FrameMakerScriptingSupport.dll: 10370000 0025b000
ExtendScript.dll: 105d0000 000a6000
ScCore.dll: 10690000 00091000
RoboHelpPublish.dll: 10840000 00042000
AdobeCaptivatePlugin.dll: 10890000 0004a000
AdobeIllustratorPlugin.dll: 108e0000 00030000
mapper.dll: 10910000 00057000
masterpages.dll: 10970000 00036000
PhotoshopPlugin.dll: 109b0000 00031000
RHFrameMakerServer10.dll: 109f0000 00032000
RoboScreenCapturePlugin.dll: 10a50000 00031000
tablesort.dll: 10a90000 00037000
TextEditorPlugin.dll: 10ad0000 00031000
WebWorks.FrameMaker9.Client.dll: 10b10000 0003b000
AdobeSWFL.dll: 10b60000 00843000
OLEACC.dll: 74c80000 0002c000
CRYPT32.dll: 77a80000 00095000
MSASN1.dll: 77b20000 00012000
urlmon.dll: 113c0000 00128000
mscms.dll: 73b30000 00015000
DSOUND.dll: 73f10000 0005c000
dbghelp.dll: 59a60000 000a1000
mlang.dll: 75cf0000 00091000
icm32.dll: 66e90000 00041000
WINTRUST.dll: 76c30000 0002e000
IMAGEHLP.dll: 76c90000 00028000
wdmaud.drv: 72d20000 00009000
msacm32.drv: 72d10000 00008000
MSACM32.dll: 77be0000 00015000
midimap.dll: 77bd0000 00007000
schannel.dll: 767f0000 00028000
RASAPI32.dll: 76ee0000 0003c000
rasman.dll: 76e90000 00012000
TAPI32.dll: 76eb0000 0002f000
rtutils.dll: 76e80000 0000e000
msv1_0.dll: 77c70000 00025000
cryptdll.dll: 76790000 0000c000
sensapi.dll: 722b0000 00005000
mswsock.dll: 71a50000 0003f000
rasadhlp.dll: 76fc0000 00006000
hnetcfg.dll: 662b0000 00058000
wshtcpip.dll: 71a90000 00008000
appHelp.dll: 77b40000 00022000
cscui.dll: 77a20000 00054000
CSCDLL.dll: 76600000 0001d000
browseui.dll: 75f80000 000fd000
ntshrui.dll: 76990000 00025000
ATL.DLL: 76b20000 00011000
shdocvw.dll: 7e290000 00173000
CRYPTUI.dll: 754d0000 00080000
=== Windows Relocation Information End ===
=== Windows Exception Information Begin ===
[Exception Record]
0012be90: c0000005 00000000 00000000 103c150c
0012bea0: 00000002 00000000 00000000 0001003f
0012beb0: 00000000 00000000 00000000 00000000
0012bec0: 00000000 00000000 ffff027f ffff0100
0012bed0: ffffffff 106c2676 05d8001b 00000000
[Exception Context]
0012beac: 0001003f 00000000 00000000 00000000
0012bebc: 00000000 00000000 00000000 ffff027f
0012becc: ffff0100 ffffffff 106c2676 05d8001b
0012bedc: 00000000 ffff0023 00000000 00000000
0012beec: 00800000 00800080 ffff0080 00000000
0012befc: 80000000 0000c003 00000000 4004e000
0012bf0c: 00000000 e8000000 00004004 00000000
0012bf1c: 4004c000 00000000 e8000000 00004004
0012bf2c: 00000000 7fffc000 00000000 00000000
0012bf3c: 0000003b 00000023 00000023 00000000
0012bf4c: 1ff10000 00000000 1ff10000 0012c264
0012bf5c: 00000000 0d433820 103c150c 0000001b
0012bf6c: 00250212 0012c178 00000023 0100027f
0012bf7c: 05d80000 106c2676 0000001b 00000000
0012bf8c: 00000023 00001fa1 0000ffff 00000000
0012bf9c: 00000000 00000000 00000000 00800080
0012bfac: 00800080 0000ffff 00000000 00000000
0012bfbc: 80000000 0000c003 00000000 00000000
0012bfcc: e0000000 00004004 00000000 00000000
0012bfdc: e8000000 00004004 00000000 00000000
0012bfec: c0000000 00004004 00000000 00000000
0012bffc: e8000000 00004004 00000000 00000000
0012c00c: c0000000 00007fff 00000000 0000002b
0012c01c: 00000000 00000433 00000000 00000000
0012c02c: 40240000 00000000 00000000 00000000
0012c03c: 8a45f1c8 00000001 00000001 00000000
0012c04c: 8054c127 00000000 34306847 00000000
0012c05c: a201c954 bf802b2f 00000000 00000000
0012c06c: 408fe000 00000000 00000000 ba338540
0012c07c: 00000000 806e7410 8968bb20 a201ca74
0012c08c: 00000000 806e7427 00000008 0377de70
0012c09c: 0377df0a 0377de70 77f6797d 0377e0c4
0012c0ac: 00000000 7c9c6ec8 0377e0c4 77f64de0
0012c0bc: 00000000 0377e0a0 77f67abb 0377e0c4
0012c0cc: 0377de94 7c9c63f0 7cbcfef4 77f67ad4
0012c0dc: 77f64de0 0377e0c4 006f0053 00740066
0012c0ec: 00610077 00650072 004d005c 00630069
0012c0fc: 006f0072 006f0073 00740066 0057005c
0012c10c: 006e0069 006f0064 00730077 0043005c
0012c11c: 00720075 00650072 0074006e 00650056
0012c12c: 00730072 7c90cffa 77dd6c03 00000b2c
0012c13c: 00000002 0377e030 77f643e0 0000ffff
0012c14c: 0377e07c 00000004 00000002 0377eb70
0012c15c: 7c9c94f8 77f643ed 7c9c94f8 00000004
0012c16c: 00000000 0377e07c 00000b2c
=== Windows Exception Information End ===
=== Windows Stack Traceback Begin ===
=== Windows Stack Traceback End ===
Regards,
Valee

Thanks for your swift response. Here is my small script.
var doc = app.ActiveDoc();
var tbl = doc.FirstTblInDoc;
while (tbl.ObjectValid()){
$.writeln ("Loop through doc tables: " + tbl.ObjectValid());
tbl.NextTblInDoc
My another small script is:
alert("Hi Valee");
I am trying to run it from my FrameMaker 10 (Version: 10.0.1.402). Also I have updated the latest patch versions.
Regards,
Valee

Error message:printhead appears to be missing, not detected, incorrectly installed or incompatible

new error message: "printhead appears to be missing, not detected, incorrectly installed or incompatible". I already tried restarting several times and have uninstalled and reinstalled all of the ink cartridges. Still receive same error mesage.

Hey walter,
I would advise performing the steps in the document linked below that addresses the printhead failure message you are receiving in this printer model. Let me know how these steps go.
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02899429&tmp_task=solveCategory&cc=us&dlc=en&lc...
I hope this helps,
Jason
-------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------
I am not an HP employee.

Syslog error - WAAS-SYS-3-900000: e1000bp: eth5: e1000bp_clean_tx_irq: Detected Tx Unit Hang

Similar Messages

Maybe you are looking for