FragglePete Posted January 30, 2019 Posted January 30, 2019 Took the opportunity to update our PaperCut MF server last week - the new features in 18.3 looking good and had our Resources Tech excited as you can start charging for things like staples within PaperCut. However, since doing the usual 'over the top' upgrade with this version (up from 18.2.6), the scripts that we run on this server using PaperCuts Server-Command command line now run extremely slowly. Like really slowly. A script that use to take a minute to run beforehand now takes over 10 minutes to complete! It's causing all sorts of grief as we reset the Student shared account PIN codes every hour, then publish these to a website that staff access to give out the code that allow student to prints. We've been running like that for nearly 5 years now with no issues and now can't publish these codes for up to 15 minutes now. Anybody else noticed anything with this release? I've got Konica asking the question but all PaperCut are saying is that 'PaperCut has got bigger, and so should our sever we run it on. Consider migrating to SQL !' WTF? Looking to downgrade if this carries on - but just seems barking in my book! Pete
MicrodigitUK Posted January 30, 2019 Posted January 30, 2019 We have upgraded to 18 and run the scripts. I haven’t had any reports of the codes not being published. But then I haven’t checked. Will have a look tomorrow and get back to you. 1
MicrodigitUK Posted January 30, 2019 Posted January 30, 2019 Only upgraded it last week so could be doing the same thing as yours. We still use the internal DB also. No full SQL.
MatthewL Posted January 30, 2019 Posted January 30, 2019 No issues and I have much larger installs using the DB and not SQL and its fine. Just on the codes for the kids, they can access and randomly generate their own code from within the user portal. I've got one site setup like this so they have cards and AD login but also it generates them a PIN, locked down many functions in the user portal but they can get the pin and generate a new one if they don't like it but they can also see their current one. Reduces calls massively.
Sylv3r Posted January 30, 2019 Posted January 30, 2019 18.3.6 was released today that may fix your issues. 1
FragglePete Posted January 30, 2019 Author Posted January 30, 2019 Only upgraded it last week so could be doing the same thing as yours. We still use the internal DB also. No full SQL. The first script (Pincode Reset) used to take 34 secs to complete - now takes 4mins 37 secs. The second script (JSON Export) used to take 1min 15secs to complete - now takes 10min 29 secs !!!! The only change is upgrading to 18.3.5 where I can pinpoint exactly the point at first run of the scripts where it takes this extra time. I've got another script, based on Powershell which I use to extract card data from PaperCut DB and insert it into a field with AD. This script was a bit lazy but it took 15 minutes to run before but it work, now takes over an hour! I guess I could try the 18.3.6 update - what have I got to loose? However, more worried at this known issue on their website: https://www.papercut.com/kb/Main/KnownIssues/#ipc-15040 PC-15040: Some Print scripts stop working after upgrading to 18.3.2. Some Print scripts stop working after upgrading to 18.3, you could be seeing an issue that could be related to the JS engine upgrade we included in this version. If you see the issue, please contact us with your script along with details about the behavior you are seeing. That would help us provide you with a fix for the issue. PaperCut have told Konica that we need to migrate to SQL - we're running 14 MFD devices from the server, and a multitude of printers with the VM having 10Gb assigned with 4 VCPUs. PaperCut itself is using 4Gb of that memory. Never had a problem before. May have to downgrade back to what we were on before - it's a bit convoluted to do so, but will do so if need be. Seems silly. Pete
MatthewL Posted January 30, 2019 Posted January 30, 2019 PaperCut don't recommend SQL for small scale installs.
FishCustard Posted January 30, 2019 Posted January 30, 2019 PaperCut don't recommend SQL for small scale installs. It's a constant vs linear issue - there's a constant overhead to running SQL, but that overhead is cancelled out by linear gains in performance for larger installs. For smaller ones the constant overhead wipes out any benefits.
FragglePete Posted January 31, 2019 Author Posted January 31, 2019 Any reason not to migrate to SQL? No real reason I guess. Just bit of planning to do it and it'll make a fun project I guess. More frustrating that this has happened. I'm better versed at MySQL so that'll be my plan. Pete
FragglePete Posted February 1, 2019 Author Posted February 1, 2019 Just noticing something. If I run something like 'server-command.exe list-user-accounts' within the PaperCut directory I get as expect the list of users, then it pauses for about 5 seconds and then drops back to a flashing cursor. Bit odd, its as if it's waiting for something the exits. So, just out of curiosity, I restored the VM from backup to another Host (gotta love Veeam), but disconnected it from the network (so it obviously doesn't fight with the running server), logged in and ran the same server-command. This time, list is displayed and drops straight back to a flashing cursor. No pause, no waiting, bang - ready to go again. This is why the scripts we run are taking so long, the scripts are essentially pausing 5 seconds after each time the server-command is called in the batch file - which loops through all the accounts (or the users in another case) - so listing through the 30 or so shared accounts the first script resets the PIN number of is adding some 150 seconds to the script! Would someone be willing to do the same on their install for me - run the command and see if it drops straight to a flashing cursor or does it pause ? Pete
Big_Ted Posted February 1, 2019 Posted February 1, 2019 raise a ticket to [email protected] Fraggle. Report the 5 second issue and quote pc-15205 in the subject. You are probably doing nothing wrong so don't waste too much time trying to fix it 1
FragglePete Posted February 1, 2019 Author Posted February 1, 2019 raise a ticket to [email protected] Fraggle. Report the 5 second issue and quote pc-15205 in the subject. You are probably doing nothing wrong so don't waste too much time trying to fix it Appreciated - Konica are aware and they look after our support on PaperCut - they have a direct line to iTS so hopefully once I can demonstrate it to them they can get the ball rolling. What's PC-15205? - couldn't see that in their KB articles Thanks Pete
Big_Ted Posted February 2, 2019 Posted February 2, 2019 it would be papercuts internal ref for the issue you see. If you go via Konica make sure they tell iTS about the ref so they can tell papercut.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now