Ricoh 2022 - Fail in a set of a certificate by FLASH.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sylerner
    • May 2025

    #1

    [Error Code] Ricoh 2022 - Fail in a set of a certificate by FLASH.

    I have a Ricoh Aficio 2022SP that was recently updated with what the web site claims to be the latest firmware for every system in the copier.

    Problem is, ever since these multiple firmware updates were installed, the syslog keeps showing lines like this after it reports that ipp was enabled:

    #[httpd(90)]11/07/22 05:25:14 Fail in a set of a certificate by FLASH. INFO:


    While not an error, a new line that wasn't in the log prior to this problem immediately follows it (it used to say "nrs disabled")

    #[httpd(90)]11/07/22 05:25:14 nrs(2) enable. INFO:


    Any idea what could be causing this?

    One more piece of information.

    While I have no idea if this is new or was always like this, going in with telnet shows that the system thinks that there are three network devices.

    This may account for it now creating two network routing services (nrs) that it didn't before.

    msh> autonet priority
    AutoNet interface priority
    1: Ethernet(ether)
    2: IP over 1394(ip1394)
    3: IEEE 802.11b(wlan)


    Any help in figuring out what is going on would be greatly appreciated.

    Thanks!
  • TonerMunkeh
    Professional Moron

    2,500+ Posts
    • Apr 2008
    • 3865

    #2
    Re: Ricoh 2022 - Fail in a set of a certificate by FLASH.

    How come you did the update in the first place? Were you fixing any particular fault?
    It's 106 miles to Chicago. We've got a full tank of gas, half a pack of cigarettes, it's dark and we're wearing sunglasses.

    Hit it.

    Comment

    • sylerner

      #3
      Re: Ricoh 2022 - Fail in a set of a certificate by FLASH.

      The copier is being heavily used for printing (using postscript) by several linux systems.

      The problem was that about 5% of the time a .pdf file was printed from Adobe Reader/Acrobat, the printer would hang and require the main power switch to be shut off, since the normally used power button didn't work, while the network activity light would be left flashing.

      Attempts to cancel these jobs from the touch screen would fail, with the printer being shown as being offline and unresponsive to hitting the online button.

      While not certain, it seems that this problem may have started with a different firmware update about a year ago, to enable the 2022 to save to a windows server that had been upgraded and would only accept encrypted SMB connections, which the original 2022 firmware couldn't do.

      So it was hoped that by getting all of the firmware in sync with the final versions that were released for the 2022 that this problem would be fixed.

      Don't know yet if the printing problem was fixed or not, but these changes in the syslog leave me wondering if I have a bad mix of firmware versions, or if while doing some physical maintenance at the same time (ADF problems, checking that the HDD and RAM connections were tight, etc.) I may have caused the system to suddenly think it had three network interfaces instead of one (but again, it may have had that problem before the syslog issue came along).

      It was a double pain because the 2022 requires a PCMCIA card for firmware upgrades, and my new(ish) laptop doesn't have a slot for PCMCIA. Fortunately, I was able to borrow another laptop and take care of the update.

      So lots of questions, a dash of uncertainty as to how far back some of the oddities I've found date to, and a lack of comfort as to the potential problems that may be lurking behind the syslog error.

      Other than that, just another lovely summer day.

      Any ideas on how to proceed will be greatly appreciated.

      Comment

      Working...