Update: 7 PM
All printing services should be restored. The original scheduled downtime at 7 PM has been canceled.
Update: 640 PM
These was an unexpected issue with this print server around 5:30 today. We are investigating the issue and will role the maintenance into this downtime. We apologize for the inconvenience.
We will be bringing down a DawgPrints server for maintenance this Friday (10/3) night at 7 PM. The process will impact most of DawgPrints across campus. We expect the downtime to be roughly 30 minutes.
Thank you for your understanding.
-Your DawgPrints Team
Update at 11:30 AM:
We have implemented an fix for this issue and have successfully tested that fix on machines that were previously reporting an error.
If you are still experiencing any issues printing, please email us at: firstname.lastname@example.org
We are aware of an issue impacting some of the DawgPrints printer across the campus.
We are actively investigating the root cause and we will update this post once we know more.
We apologize for the inconvenience and appreciate your understanding.
-Your DawgPrints Team
All issues related to the Richo 5200’s should now be resolved.
We are aware of an issue impacting several Richo 5200’s across campus.
We are looking into the issue and will update this post when we have more information.
Update @ 5:13PM
All services should now be restored.
We need to restart the Dawg Prints servers in an effort to address a specific issue. The service interruption should be less than 10 minutes.
Thanks for your patience.
Update 12:04 – it appears services have returned to normal
Update 9:40 – major HFS services are online but our billing server is still getting error messages. We’ve emailed HFS to seek confirmation that the specific services DawgPrints depends on were restarted.
We’ve got reports that various billing related services are down.
As near as we can tell this relates to the Husky Card system not currently allowing charging.
We’ve got an email to HFS to confirm, and will update the blog when we hear back.
UPDATE 11:27: the vendor informs me that “mobile print” services should not have experienced any interruption due to the current difficulties. We continue to work towards resolving this to provide maximum capacity but all user complications should have been resolved as of 8:37
UPDATE: 9:19: Regular printing operations work normally, but there continues to be a problem isolated to “mobile print” users on selected release stations. We’ve contacted the vendor and will repair this functionality shortly. Thank you for your patience as we continue to beta test the mobile print service.
UPDATE: 8:37: an unexpected service failure left several labs without DawgPrints service. The service has been fixed and the lab’s report working connectivity. Thank you for your patience in this
UPDATE 8:07: both print servers are set. Please notify us at email@example.com if you experience any issues.
Note that all release stations will experience a delayed swipe-to-login for the first login only
UPDATE 8:01: the primary print server is up and running. All library print stations should be working.
There was a minor hiccup with the secondary print server and we’re restarting it again. It should be up within 5 minutes
UPDATE: Maintenance has began
We’ll be bringing the DawgPrints servers down briefly on Tuesday May 20th for some brief maintenance
We expect to start around 7:45 AM and downtime should last less than 15 minutes.
Note that all release stations will experience a delayed swipe-to-login for the first login only after this maintenance occurs.
We will update this post tomorrow morning both before and after the maintenance.
Please email us at firstname.lastname@example.org if you have any questions or concerns,
UPDATE 3:58 – print services are restarted and the billing plug-in issue should be resolved. PLEASE NOTE that the very first time a card is swiped there will be a message about re-connecting to either BORIS or NATASHA. This is normal and caused by the system maintenance we just performed. Subsequent swipes should work as one would expect.
We’ve received several reports of issues with the billing plug-in.
We’re going to bring the print servers down momentarily (~3:50) in an attempt to fix. We’ll update this blog soon.
We’ll be restarting the DawgPrints servers briefly tomorrow (24 April) around 7:45 AM. Downtime should be no longer than 10 minutes.
8:47 UPDATE: unfortunately we will need to once again restart a single DawgPrints server. Downtime should be less than 5 minutes and have minor effect.
8:50 UPDATE: all servers are online and services are started. Please note some lab locations may take a moment to re-establish a connection with BORIS. This is expected to occur *once* for the first user of a station and not subsequently.
We’ve received several reports of issues with swiping cards. Users report an error message
“billing plug-in returned no results”
Reports indicate this is a periodic problem and that some (but not most) payments successfully process.
We’re looking into this now.
If you have anything to report in addition to the above information please contact us at email@example.com
12:35 – UPDATE we’ve begun a support call with the vendor. Will update this shortly
2:13 – UPDATE the support call continues. We have not given up
3:57 – UPDATE the vendor suspects this may be an underlying problem with the OS. We’ll be taking the servers offline momentarily for a few minutes
4:27 – UPDATE we’re at a working state now. PLEASE NOTE that all release stations will *appear* to time out on the first swipe. During this time the release station is re-conencting to the print servers. Subsequent swipes should behave normally.
The vendor will continue to work towards determining the root cause of this, and we will be checking firstname.lastname@example.org overnight to ensure repeated outages do not occur.
UPDATE: UW-IT reports weblogin issues were resolved at 11:45 AM.
UW-IT is in the midst of resolving some issues with weblogin. During this time scan to email users may experience delays when authenticating.
To get the most updated status of this issue see the UW-IT Outages page