Invalid packet length error in logs

For over a week now I’ve been getting the following error in my log once a minute:
Invalid packet (too large) length=17247
I’ve seen it stop for maybe an few hours a couple times but otherwise it’s constant. Anyone know how to track down who or what is sending this invalid packet?
Thanks

Hi,
your router will drop the over sized packet if the DF flag is set.  However, it will return a message to the originating device showing packet oversize.
You can try setting the router logging to debug and verbose.  This should return the originating IP.  One other thing that you can do is take a close look at any devices  that you have setup.
Additionally, you can try changing the MTU on the router but this could result in performance 
degradation.  Alternatively, if you can identify the originating device, you can try changing
 the MTU there as well.
HTH 
Houtan

Similar Messages

  • Invalid Packet Length?

    Hi,
    We have a SessionBean that is being called very often. Whenever
    the SB method is called, we do a select from dual to access a
    sequence.
    After a while, we start getting a SQLException (see below for
    stacktrace) with "Invalid Packet Length" message.
    The first exception is on the PreparedStatement.close() and the
    following exception are in the Connection.prepareStatement()
    method.
    Does anybody have an idea of the cause of the problem?
    java.sql.SQLException: Io exception: Invalid Packet Lenght
    at oracle.jdbc.dbaccess.DBError.throwSqlException
    (DBError.java:168)
    at oracle.jdbc.dbaccess.DBError.throwSqlException
    (DBError.java:210)
    at oracle.jdbc.dbaccess.DBError.throwSqlException
    (DBError.java:323)
    at oracle.jdbc.driver.OracleStatement.close
    (OracleStatement.java:604)
    at oracle.jdbc.driver.OraclePreparedStatement.privateClose
    (OraclePreparedStatement.java:290)
    at oracle.jdbc.driver.OraclePreparedStatement.close
    (OraclePreparedStatement.java:235)
    at
    itc.epc.components.docManager.SBDocManagerBean.getUniqueKey
    (SBDocManagerBean.java:2048)
    at
    itc.epc.components.docManager.SBDocManagerBean.createDocument
    (SBDocManagerBean.java:156)
    at
    itc.epc.components.docManager.SBDocManagerBean.createDocument
    (SBDocManagerBean.java:101)
    at
    itc.epc.components.docManager.SBDocManagerBean.createDocument
    (SBDocManagerBean.java:251)
    at
    com.sssw.gen.ejb.EJB_DocManagerDeployed.itc.epc.components.docMan
    ager.SBDocManagerObject.createDocument
    (SBDocManagerObject.java:487)
    at
    com.sssw.gen.ejb.EJB_DocManagerDeployed.itc.epc.components.docMan
    ager.SBDocManagerObjectPOATie.createDocument
    (SBDocManagerObjectPOATie.java:1038)
    at
    itc.epc.components.docManager._SBDocManager_Stub.createDocument
    (_SBDocManager_Stub.java:2660)
    at itc.fs_model.parser.ModelBuilder.storeReferenceFileInfo
    (ModelBuilder.java:827)
    at
    itc.fs_model.parser.ModelBuilderCreateMode.createReferenceFile
    (ModelBuilderCreateMode.java:295)
    at itc.common.xmlparser.XMLParser.exportReferenceFile
    (XMLParser.java:467)
    at itc.common.xmlparser.XMLParser.exportOneScenario
    (XMLParser.java:319)
    at itc.common.xmlparser.XMLParser.exportScenarios
    (XMLParser.java:242)
    at itc.common.xmlparser.XMLParser.traverseTree
    (XMLParser.java:210)
    at itc.common.xmlparser.XMLParser.parseFile
    (XMLParser.java:135)
    at itc.fs_model.parser.ModelBuilder.start
    (ModelBuilder.java:628)
    at itc.fs_model.parser.ModelBuilderCreateMode.start
    (ModelBuilderCreateMode.java:351)
    at
    itc.epc.components.docManager.SBDocManagerBean.createScenario
    (SBDocManagerBean.java:1547)
    at
    com.sssw.gen.ejb.EJB_DocManagerDeployed.itc.epc.components.docMan
    ager.SBDocManagerObject.createScenario
    (SBDocManagerObject.java:718)
    at
    com.sssw.gen.ejb.EJB_DocManagerDeployed.itc.epc.components.docMan
    ager.SBDocManagerObjectPOATie.createScenario
    (SBDocManagerObjectPOATie.java:968)
    at
    itc.epc.components.docManager._SBDocManager_Stub.createScenario
    (_SBDocManager_Stub.java:1845)
    at com.interfacing.epc.ui.admin.UploadModelAction.perform
    (UploadModelAction.java:167)
    at
    org.apache.struts.action.ActionServlet.processActionPerform
    (ActionServlet.java:1787)
    at org.apache.struts.action.ActionServlet.process
    (ActionServlet.java:1586)
    at org.apache.struts.action.ActionServlet.doPost
    (ActionServlet.java:510)
    at javax.servlet.http.HttpServlet.service
    (HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service
    (HttpServlet.java:853)
    at com.sssw.srv.resources.AgWarResource.doServletDispatch
    (AgWarResource.java:796)
    at com.sssw.srv.resources.AgWarResource.service
    (AgWarResource.java:572)
    at com.sssw.srv.resources.AgWarURLResource.perform
    (AgWarURLResource.java:114)
    at com.sssw.srv.http.httpd.perform(httpd.java:4560)
    at com.sssw.srv.http.Client.processRequest(Client.java:883)
    at com.sssw.srv.http.Client.loop(Client.java:1217)
    at com.sssw.srv.http.Client.runConnection(Client.java:1421)
    at com.sssw.srv.http.Client.run(Client.java:1381)
    at java.lang.Thread.run(Thread.java:484)

    Hi,
    your router will drop the over sized packet if the DF flag is set.  However, it will return a message to the originating device showing packet oversize.
    You can try setting the router logging to debug and verbose.  This should return the originating IP.  One other thing that you can do is take a close look at any devices  that you have setup.
    Additionally, you can try changing the MTU on the router but this could result in performance 
    degradation.  Alternatively, if you can identify the originating device, you can try changing
     the MTU there as well.
    HTH 
    Houtan

  • Sparseimage Fails Verification with Invalid Key Length error.

    I recently have been having some trouble with my computer. Every time I log out of my account, all of my preferences reset. This just now started happening. It was working fine, then all of a sudden it started to do this. This only happens on my account and doesnt with the root account. On looking up solutions, I discovered that I should verify my home directory image. I logged in as a different user (root) and used disk utility to verify it. However it failed saying "invalid key length" and "Error: The underlying task reported failure on exit". When I try to repair it, it gives me the same error. I backed up my system using superduper to an external drive a while back and verified the sparseimage file that I backed up. It failed with the same error.
    When I verify my harddrive it passes with no problem. Only my sparseimage file is corrupted. I would try diskwarrior but I cant afford it right now.
    Any help would be greatly appreciated. Thanks.
    Macbook   Mac OS X (10.4.9)   100gb hd; 1gb ram; Triple-Boot(OSX-Linux-Vista)

    Would that mean that I can't turn off filevault? Way I see it is that since the image file is corrupted, I would try to have filevault unencrypt it and see if it somehow fixes it. (Since there will be no longer a filevaut image to be corrupted). All of my data in the image file seems to be fine. Everything is still there and I can access everything.
    I was also thinking that I might be able to just copy everything in the image to my external, then deleting the account and create a new one, coping everything back over when im done.
    I know I probably sound like a noob, but im really not. Ive had a lot of experience with my computer, just not this sorta thing. Thanks for your help.

  • Invalid Key Length error after 10.4.3 install/10.4.4 update

    After installing Mac OS X, version 10.4.3 from CD, and upgrading to version 10.4.4 via Software Update, ran Disk Utility, verify disk, from DU on startup disk and got following message: "...Invalid key length...The volume Macintosh HD needs to be repaired. Error: The underlying task reported failure on exit...1 HFS volume checked...Volume needs repair." Tried rebooting from 10.4.3 install CD and running Disk Utility, First Aid, from CD to repair startup disk. After trying 3 times, First Aid halted and could not repair problem. Purchased Disk Warrior 3.0.3 CD, booted from DW CD, and DW also could not "rebuild" startup disk. Have purchased Drive Genius 1.2 CD from Prosoft to try to repair startup disk. If that fails, is only recourse to backup software on startup disk to external hard drive, and do erase and re-install of 10.4.3/10.4.4 software to cure problem? Please provide help!
    iMac G-4,800Mhz,512M Ram,60G HD   Mac OS X (10.4.4)  

    Dear Andrew Penner, Thanks for reply. I will try re-install of 10.4.4 using the long version in Apple downloads rather than the abbreviated, tailored 10.4.4 version obtained thru Software Update. The suggestion to check Library/Receipts is useful. Since Mac OS 10.4 has been out nearly a year, I know someone must have experienced a similar error message by now (i.e. "Invalid key length") when running Disk Utility with new versions of 10.4. If only recourse is to "reinstall" the software, one wonders what is causing the "corruption" in the data in the first place. Puzzling. Will post result after reinstall and retest. I noticed the version of Disk Utility on my 10.4.3 Install CD is 10.5 whereas the version of DU on my hard drive after the 10.4.4 update is 10.5.3. Is that a problem? JaxJT
    iMac G-4,800Mhz,512M Ram,60G HD   Mac OS X (10.4.4)  

  • Packet Length errors

    We are getting frequent partition crashes in various service objects with
    this type of exception:
    FATAL ERROR: Packet length extracted from data is illegal (0x6d70).
    Class: qqsp_ImplementationException
    Error #: [501, 93]
    Detected at: qqcm_FortePacket::ReadHeader at 1
    Error Time: Tue May 22 17:43:54
    Exception occurred (locally) on partition "a_service_server_cl0_Part9",
    (partitionId = C83527E0-0DB4-11D5-B381-ED2750E6AA77:0x69ba, taskId =
    [C83527E0-0DB4-11D5-B381-ED2750E6AA77:0x69ba.5]) in application
    "a_service_server_cl0", pid 4091 on node tronsha4 in environment
    mdlprime.
    We are running Forte 3.0.M.6, compiled, on Solaris 2.6 with the most recent
    patches. I haven't found anything on this in the tech notes or the
    forte-users archive. I would suspect some port scanner activity, but this
    system is not attached to the public network, so I don't think that is
    possible.
    Any information would be greatly appreciated.
    Thanks,
    Mike Lapeyre
    EDS bluesphere

    Do you have any docs or infos with "mib" oder something i should check is the ap is a good condition. i have the problem that sometimes some aps "die" -> i have to reboot them, the problem is that i have to drive to them, they are not in my office.
    hope you can help me
    bernhard

  • Java.sql.SQLException: invalid packet length

    can i get more info on this , the application has been running for some time , we are now getting the above message

    What version is the DBMS? Off hand, if you get this type of error by backing the Java version in or out,
    I'd file an official bug and let the driver and JVM folks figure it out...

  • Powerbook won't start - Disk Utility error "Invalid Key Length" - help plz!

    Hello
    I am having problem with my Titanium powerbook. Since it was refurbished I have only been using it for internet browsing and email and I don't know why it suddenly started freezing. After a couple of freezes it stopped starting up. I don't know why, as I wasn't doing anything unusual. I have run a few checks and don't know how to proceed. Please help.
    This is what I have done so far:
    1. Tried to start up in Safemode. Made the startup sound but then went dead.
    2. I tried Single User Mode and did fsck -fy and the results were:
    ** /dev/rdisk0s10
    ** Root file system
    ** Checking HFS Plus volume
    ** Checking Extents Overflow file.
    ** Checking catalogue file
    Invalid key length
    (4, 135)
    ** volume check failed
    localhost:/ root# Firewire (OHCI) Apple ID 18 built-in: no valid self IDs for more than 2 minutes after bus reset.
    3. No problems were detected by the Hardware Test disk.
    But the powerbook still won't start up properly. I can't get past the blue screen with the 'thinking' (rotating) circle icon (pinwheel?).
    4. When I try to access the computer using a firewire cable the hard disk doesn't appear on the host computer.
    5. I tried Disk repair Utility from startup using a disk but got the same result as with fsck -fy.
    Any ideas?

    Hi, Can't. Your hard drive's directory is damaged in a way that exceeds the limited repair capabilities of Disk Utility or fsck. DiskWarrior can fix "invalid key length" errors, as this short FAQ explains. If you have DiskWarrior, use it to make the repair. If you don't, you can either buy DW, or reformat the hard drive with Disk Utility and start over. Note that reformatting the drive will erase everything on it, so if there's any important, un-backed-up data on it that you can't afford to lose, buying DW will be the better option for you.
    Message was edited by: eww

  • Invalid Packet Lenght, JDBC, Java6 update 85

    All,
    I applied the CPU patchset for October 2014.  The java update produced the following:
    (Java.sql.SQLException: Invalid packet length)
          org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:261)
    --No errors are produced when backing out to Java 6 update 81.
    Driver Information:
    Manifest-Version: 1.0
    Ant-Version: Apache Ant 1.6.5
    Created-By: 1.5.0_51-b10 (Sun Microsystems Inc.)
    Implementation-Vendor: Oracle Corporation
    Implementation-Title: JDBC
    Implementation-Version: 11.2.0.3.0
    Repository-Id: JAVAVM_11.2.0.4.0_LINUX.X64_130711
    Specification-Vendor: Sun Microsystems Inc.
    Specification-Title: JDBC
    Specification-Version: 4.0
    --Should I update the driver or is this an issue with the new update?  Any help is appreciated.

    What version is the DBMS? Off hand, if you get this type of error by backing the Java version in or out,
    I'd file an official bug and let the driver and JVM folks figure it out...

  • Invalid key length on hard drive. Can this be fixed?

    Hello,
    I have a question about an error I am receiving with a hard drive I have been using for a few months on an imac G3 (the slot loading version). I bought this used 80 GIG hard drive on ebay for a friend of mine and I helped him transfer all his data from his older 9 GIG drive to this newer 80 GIG drive that I bought for him on ebay. I simply cloned the 9 GIG drive onto the new drive using Carbon Copy Cloner. There is not a lot of data on the drive - only about 3 GIGs of data.
    The drive is the only drive in the computer (an imac G3) and therefore it is the startup drive. The operating system on the drive is OS9. All was working fine for a few months until just last week. Now I am receiving this following error:
    error message:
    The disk "Macintosh HD" appears to be damaged. Use a disk repair utility to repair the disk.
    And so I used the disk utility built into OS9 to see if I could repair the problem. (I think OS9's disk utility is called "Disk First Aid")
    When using OS9s disk utility (I think it is called "Disk First Aid") the following report is issued:
    Problem: Invalid key length, 4,943
    Test done. Problems were found but Disk First Aid cannot repair them.
    My questions are:
    What is an "Invalid key length"?
    How serious is this?
    What would cause this?
    Could this have been caused by the physical condition of the disk or possibly by the software on the disk?
    Would re-formatting the drive fix it? (Of course I would try to save any data first onto another disk)
    Or is it risky to continue to use this disk even after reformatting it?
    I guess I have a lot of questions here and if anyone could make any suggestions or comment on why "Invalid key length" errors happen I would really appreciate it. Thanks:)
    Here are some details:
    When I bought the 80 GIG hard drive from ebay the first steps I took were to format the drive using OS9's "drive setup", load the OS9 drivers and then I verifed the disk. The disk seemed to be fine. Then I cloned his old drive onto this 80 GIG drive using Corbon Copy Cloner. I was sure the 80 GIG drive was in a healthy state at that time and I trusted it enough to give it to my friend for his startup drive. Now that the drive has failed with his data and programs, I feel pretty bad. How could this "Invalid key length" error occur?
    Should I go back to the person who sold me the drive on ebay and ask for a refund? Or are "Invalid key length" errors a common occurance with hard drives that should just be accepted? Or might it possibly be the contents (data) on my friend's disk that caused this error.
    It has been suggested to me to use "Tech Tools Pro" or "Disk Warrior" to repair the disk. Hopefully that might repair the disk. Unfortunately these programs are too expensive for this purpose because they would cost more than the computer actually costs (its an old imac G3 computer). I found a service that would run Disk Warrior on the disk to repair it for a $50 fee. Still, that is also not worth it as the computer may not even be worth $50.
    Here are some specifications:
    80 GIG drive specs: SEAGATE BARRACUDA 7200.7 80GB hard drive
    computer: imac G3 (slot loading version)
    OS: Mac OS9
    Thank you for any suggestions especially as to whether I should attempt to return the hard drive or look for a refund for this hard drive or attempt to reformat the drive and try again (backing up the data first).
    I also question the source of all the data on my friends computer. If he had the original operating system disks (which he said didn't come with his computer when he purchased it second-hand), I could have easily re-installed the OS and the applications. But he doesn't have any disks. That serves me right for having to deal with trying to help out someone who has software from a questionable source. I'm never doing that again. I guess that makes me guilty too as an accomplice. I don't feel very good about this
    I didn't know for sure - but I guess I should have assumed his software was illegal if he didn't have the disks - I was afraid to ask. I'm never putting myself in this possibly illegal situation again. Never again will I try to help someone out who doesn't clearly have the legal disks. Please forgive me and everyone else who reads this post. I feel shameful about this but somehow I must get myself out of this problem. I've learned a good lesson. Should I attempt to fix his computer? Or should I tell him to first buy a legal OS and software before I can help him out? You see I feel further guilt because I was the one who gave him the 80 GIG problematic hard drive that failed and I feel I should have to fix it. Can anyone offer me a bit of advice? What do I do?
    What's the right thing to do?

    Thank you Jim and Apple2Freak,
    I appreciate your comments. I am now suggesting to my friend to buy a legal OS and if that is the case I am suggesting to him to move to OSX instead of OS9. Luckily he let me know there wasn't much data on that drive that he needed to save. I am still trying to determine if I could still use this hard drive with the keylength errors if I erase it or if the hard drive has permanent damage. I am hoping that I could install OSX on it and erase the hard drive to start again.
    This imac (slot loading version) can support up to OS 10.3.9 however I might consider Xpostfacto to try to run 10.4. But then I would need to buy 10.3.9 as well as 10.4 and that would double my OS cost. I think I might just look for OS 10.3.9 only. Its not worth it for me to buy two OSes for it.
    Jim, your post was very interesting because it also pointed out that it could be an issue of bad RAM. A few months ago we installed some new second-hand RAM and I wonder if that is the cause of all these problems. I will have to check that first.
    Thanks again!

  • Invalid key length - options

    A couple months ago I had issues installing Lion on my MBP. Upon installing, I was not able to mount the hard drive because of multiple errors. Disk repair eventually worked, I used my Time Machine backup to restore, and got Lion installed. After the installation, I went to make another TM backup and my external hard drive was corrupted to the point where I had to wipe everything on it - not sure what happened with it. Because I had so much trouble getting Lion installed, I didn't mess with creating a new TM backup and wanted to wait until I wasn't so busy at work to attempt it. I did however create a bootable Lion USB drive for emergencies.
    Long story short, the MBP froze the other day and would not boot properly. Clearing the PRAM/VRAM did not help, and when I try disk utility with the bootable USB drive, it is able to verify the drive itself, but unable to mount the startup volume. When I try to verify that volume, it stops and says to repair it. When I try to repair it, it stops and tells me the volume cannot be repaired and I need to back up my files.
    However, when I go into single user mode (running fsck gives me an invalid key length error), I can see the file structure of the drive, and all of my files in read only mode. My questions is, are those files recoverable? If so, how?
    Many thanks for an thoughts

    You have a failing internal hard drive, or some other hardware fault in the mass-storage subsystem. You must replace the drive, or otherwise determine the cause of the fault, immediately. But first you need to back up your data, if it's still possible.
    There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
    1. Boot from your recovery partition (10.7 or later), a local Time Machine backup volume (10.7.2 or later), or your installation disc (10.6.8 or earlier.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
    How to back up and restore your files
    2. If you have a working Mac, and both it and the non-working Mac have FireWire ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive.
    How to use and troubleshoot FireWire target disk mode
    3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

  • "Invalid Key Length"

    Attempting to upgrade an iBook with 10.4.6 from 10.3.9 and getting an "Invalid Key Length" error during disk repair using Disk Utility.
    http://discussions.apple.com/thread.jspa?threadID=1042084
    Is there another way to get beyond this without erasing the HD?

    Yes, but you'll need DiskWarrior to fix the directory problem, since DU can't do it. Hopefully, you have a bootable backup/clone. If so, that allows you to revert to the previous good state without having to reinstall everything. Barring that, you'll have to erase the HD.
    Review these
    http://docs.info.apple.com/article.html?artnum=106941
    http://www.macmaps.com/upgradefaq.html
    http://www.thexlab.com/faqs/installswupdates.html
    http://www.thexlab.com/faqs/backuprecovery.html
    and adopt the necessary habits to mitigate what happened to you.

  • What cause this error: java.util.zip.ZipException: invalid literal/lengths?

    Hi all,
    Our application produces this error in the logs: (our JDEV is 11.1.1.4.0, WLS 10.3)
    org.apache.myfaces.trinidadinternal.renderkit.core.CoreResponseStateManager _restoreSerializedView
    SEVERE:
    java.util.zip.ZipException: invalid literal/lengths set
    at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:147)
    at java.util.zip.GZIPInputStream.read(GZIPInputStream.java:92)
    at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2266)
    at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2279)
    at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)
    at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
    at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
    I have googled this error for hours and search the forum here, but no luck. Can someone please shed some light on this error? Thanks in advance!
    Shawn

    Hi Shawn,
    Please refer the below thing i found. Hope this may help you in moving forward in resolving. I hope this issue has occured when you are deploying your application WAR.
    ======================================================================================
    Method: read()
    Class: at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:147)
    The above class comes in your exception hierarchy above.
    Reads uncompressed data into an array of bytes. This method will block until some input can be decompressed.
    Throws:
    ZipException - if a ZIP format error has occurred
    ====================================
    This also points that your WAR file is corrupt.
    Class: GZIPInputStream
    IOException - if an I/O error has occurred or the compressed input data is corrupt
    Thanks,

  • Packaging error 2 (The media contains invalid NALU length)

    Hi,
    I am trying to publish live stream from Adobe Flash client that can be viewed on iOS device.  One known issue is that the Flash client does not support AAC audio encoder when it publishes a stream, but AAC is required for iOS viewing.  Thus I am using ffmpeg to transcode the audio to work around this issue.  The setup looks like following:
                                     Publish(h.264+Speex)      Pull               Re-Publish(h.264+AAC)
    Flash Client Publisher -------------------> AMS -----> ffmpeg ---------------------> AMS
    The command line I use for ffmpeg is like this:
    ffmpeg -re -i rtmp://xxx.xxx.xxx.xxx/livepkgr/orgstream -c:v copy -c:a aac -strict -2 -f flv rtmp://xxx.xxx.xxx.xxx/livepkgr/livestream
    This setup works perfectly if the original stream is published by Flash Media Live Encoder client.  However, if the stream is published by a web page using Flash ActionScript client, the iOS won't play the stream.  The root cause is that HLS module failed to generate the proper TS file. I get the following error in the Apache server log.
    [Sat Aug 17 15:56:50 2013] [error] mod_hlshttp [500]: Packaging error 2 (The media contains invalid NALU length) when processing /hls-live/streams/livepkgr/events/_definst_/livestream/livestreamNum0.ts
    I've tried various things to narrow down the possibilities regarding what could be wrong.  Here are some of my observations:
    1) The problem has nothing to do with audio.  If I do audio streaming only, it works well.  So in various experiement, I simplified the problem by doing video stream only.  When using ffmpeg to transcoding, I used '-an' to disable audio stream.
    2) If I use ffmpeg to save the stream into MP4 file first (say 1 minute long), and then publish that file, I got the same issue when iOS device is trying to retrieve content.  The MP4 file generated is fine though.  I can view it using VLC.
    3) If I use ffmpeg to transcode H.264 to H.264 (i.e. Not to use the "copy" transcoder), it then will work.  However, because of the CPU usage constraints in my requirement, I cannot adopt this approach. Here is the command line that works:
    ffmpeg -re -i rtmp://xxx.xxx.xxx.xxx/livepkgr/orgstream  -vcodec libx264 -b:v 1000k -c:a aac -strict -2 -f flv rtmp://xxx.xxx.xxx.xxx/livepkgr/livestream
    4) In all those experiments, the m3u8 file are generated correctly.  In the stream directory I always saw meaningful size for f4f and f4x files.
    5) The iOS client is able to view the original stream fine if the original stream is H.264 video only stream. (The 'orgstream', not the one republished by ffmpeg).
    6) In all those experiements, a regular Flash viewer client is able to play the live stream with no issue.
    Since I don't have access to source code to the Apache module for HLS (mod_hlshttp), I don't know how to proceed further. I appreciate any help from Adobe engineering team who have access to source code, and give me some hint what could go wrong.  I can also provide further information regarding the published stream, e.g. the generated MP4 if it can help.
    Thanks and best regards,
    Jason
    Message was edited by: Json

    The one thing you didn't do is reset your Photoshop preferences.
    Most likely the preferences got corrupted, and reference a corrupt preset.

  • System.log fills up with bad packets errors (Multicast packet - CRC error)

    Hello,
    I've been trying to Google my problem but found no answers; hopefully someone can help me?
    Whenever I'm online, my System.logs fills up (every second, and sometimes, multiple times each second) with the following message :
    19/12/07 12:51:01 PM kernel AppleYukon2 - bad packet received. length: 60, packet status bits: Multicast packet, CRC error
    19/12/07 12:51:01 PM kernel AppleYukon2 - bad packet received. length: 60, packet status bits: Multicast packet, CRC error
    My DSL modem is connect directly into my iMac. It's a Speedstream 5360). I never have any problems connecting to the Internet and the speed I get is fine. When I configured my Network settings, I only added my PPPoE Service name username and âssword - everything else was automatically added (Ethernet configuration).
    Is there anything I should change in the Advanced Settings?
    The System.log causes me problem because it often causes the application Console to crash when I try to view it.

    I should add that this problem didn't exist when I was using Tiger.
    Also, when I called Apple Tech Support, I was simply told "just don't play with the Console".

  • Error-Invalid key length?

    My G5 osx 10.4.3 keeps crashing, Cd's don't showup.
    I've run various utilities on it, nothing fixes it.
    When running disk utility it gives message-
    Invalid key length and says volume can't be repaired.
    Also tried Techtool deluxe and disk warrior.
    Any ideas?
    Ty

    I don't see much hope knowing you tried the usual utilities. I trust you tried all the repair procedure while booted from a CD...
    If you haven't done so already, backup as much as you can on an external HD (I would even try a clone)
    Erase and zero your HD. Reinstall Tiger and retrieve as much as you can from the external HD.
    By the way, if you don't yet have an external HD, now is the time to get one that is at least as large as your internal HD. Compared to the time lost and the anguish experienced they are cheap...
    Backup regularly...

Maybe you are looking for