iPrint appliance stops communicating with identity source

Appliance 23.4.  People using printers that require authentication will randomly lose access to those printers.  They will not be able to login.  So far the only solution is to reboot the appliance.  Then everything comes back for a few weeks until the problem repeats itself.  Anyone have any thoughts?  I have run the iPrint appliance for years without any troubles and this version is the first to have this issue.

Parents
  • 0

    Does anyone have this issue still, we applied the fix microfocus-iprint-auth-1.2.0-150400.170.1.x86_64.rpm supplied by support which fixed most of them but still have a couple of 24.2.1 appliances failing. I now have one that restarting the auth service or the appliance no longer gets it working and have been back and forth with OpenText support all day. Its very frustrating on a production enviroment with hundreds of users impacted.

    Output after trying to restart the service.

    iprint:~ # systemctl status iprint-auth.service
    iprint-auth.service - Microfocus iPrint Auth Service
    Loaded: loaded (/usr/lib/systemd/system/iprint-auth.service; enabled; vendor preset: disabled)
    Active: activating (auto-restart) (Result: exit-code) since Wed 2024-05-22 15:29:35 AEST; 802ms ago
    Process: 4677 ExecStart=/opt/novell/iprintauth/bin/iprint-auth-service.sh (code=exited, status=1/FAILURE)
    Main PID: 4677 (code=exited, status=1/FAILURE)

    Any ideas would be appreciated as support seem to be a bit lost.

  • 0 in reply to 

    I thought the problem was fixed for us as everything seemed to go quiet.  But today I had users complaining about have to login multiple times again so I am reopening my support case!

  • 0 in reply to 

    Hi Ken,

    Support logged into my instance that wasn't fixed by a restart and had to drop the iPrint-Auth database for the ldap sync and I then recreated the Identity Source to our eDirectory server. Early days but it's still working fine now. Support did collect logs which they said they would check to see if they could see why the database was corrupted. Note this iPrint instance did have the fix applied before the latest issue happened.

Reply
  • 0 in reply to 

    Hi Ken,

    Support logged into my instance that wasn't fixed by a restart and had to drop the iPrint-Auth database for the ldap sync and I then recreated the Identity Source to our eDirectory server. Early days but it's still working fine now. Support did collect logs which they said they would check to see if they could see why the database was corrupted. Note this iPrint instance did have the fix applied before the latest issue happened.

Children
No Data