Too many users

[James Flanagan]

Scott, 

I have experienced a similar situation with filepro, on at least 3 different software platforms, over the years.  I have exhaustively tried to both understand and remedy this issue WITHOUT rebooting, and I will share the latest information I received from FPTech.

According to the developers, one possible cause of the phantom license issue is using kill command with the -9 argument.  This is incredibly unfortunate because as most unix admins know, most times, it is the “-9” switch that actually kills what you are trying to kill.

In the event that you want to reset the license count back to 0 (I am not aware of any function that will reset only some of the license count, so it is an all or nothing consideration), you need to get everyone off the system, and then run the following command:

ipcs -m | grep filepro

This will display the shared memory segments for filepro.  Use the ipcrm -m command to remove those shared segments, and your license count will be reset to 0.  That being said, depending upon time it takes to reboot your server hardware, by the time that you get everyone off of the system anyway, it may be more efficient to reboot.  But, now at least you can reset the license count without a reboot whenever necessary.  

Good luck, 


James Flanagan
Flantec.com <http://flantec.com/>

email:	James at Flantec.com <mailto:James at Flantec.com>
mobile:	760-458-8498
home: 	219-221-6219
text:		7604588498 at txt.att.net <mailto:7604588498 at txt.att.net>

Skype:	Flantec
ichat:	James at Flantec.com <mailto:James at Flantec.com>	

home:	1901 Cidermill Road
		Michigan City, IN 46360



> On Nov 11, 2020, at 3:03 PM, scooter6--- via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> As with many companies, we have a ton of our staff working remotely.
> They access our network via OpenVPN and work as normal via putty
> We have CentOS 7 and fP 5.6.10R4
> Internally, in the office, ssh times out in 10 minutes, but it kills the
> session entirely (at least through past years experience, we've never
> encountered this will staff working here at the office)
> But over OpenVPN, it has 10 minute timeout built in to the config but it
> doesn't kill their putty session.
> I monitor every now and then and kill them when I see this
> However, this appears to be causing a problem where we get 'too many users'
> error
> We have 95 user license, and I know that doesn't mean 95 'users' - it's
> occurrences of rclerk, etc
> But we keep getting this error occassionally and when I got it, I looked
> and we had combined, a total of 47 instances of rclerk, rreport etc running
> 
> The only solution is to reboot the server.
> 
> Is there a way, either in fP or in OpenVPN, where I can make sure it fully
> kills their session and we can stop getting this 'too many users' error?
> 
> Thanks
> Scott
> PDM
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20201111/63612a1f/attachment.html>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20201112/74e50e9b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-1.tiff
Type: image/tiff
Size: 19328 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20201112/74e50e9b/attachment.tiff>