Hi,
“state shell” complains I have too many runtimes, but I cannot find more than one runtime on my system. I actually don’t want to have more than one runtime. Is there a way to find what and where my runtimes are? How would I delete the extra runtime?
This is the error message I get:
C:\Users\root>state shell
Heads up! You've reached your runtime limit for <redacted>-org.
You can upgrade your plan or enroll in a free trial by visiting:
https://platform.activestate.com/upgrade/?org=<redacted>.
You are using 2 out of 1 available runtimes.
Opening shell for project <redacted>/Perl-5.36.0-Windows, located at C:\Users\root\Perl-5.36.0-Windows.
This shell is operating inside a virtual environment.
For editors and other tooling use the executables at: c:\Perl\exec.
✔ Project "<redacted>/Perl-5.36.0-Windows" Has Been Activated
Some background information:
- I’m not new to ActivePerl and Windows admin, but I’m new to this “state” and “runtime” scheme.
- There are two users on this PC, one for daily use, and one admin account with full permissions for system management.
- I experimented a lot with these two users and “state”, going through several rounds of state-remote-installer.exe and state clean uninstall --all until I had Perl configured the way I wanted, owned by the admin account but accessible to both the daily and admin accounts. I’m guessing that one of these rounds left a pointer to a runtime that doesn’t really exist anymore, and that’s the problem.
- I don’t intend to use “state” much, and I certainly don’t need to experiment with different runtimes. I may add a package from time to time, but that’s it. I use Perl for my personal needs; system management and photo library management.
Thanks for any help you can provide!
Martin
I see it every time I launch a shell (“state shell”), which I understand is the first thing I should do to before issuing other “state” commands. But perhaps I’m mistaken about this last statement.
Even if I don’t launch a shell, I also get the warning every time I run “state install”, “state pull”, etc.
I don’t get the warning when I run “state show”, “state use show”, “state projects”, or even “state info DateTime”.
Hello,
The runtimes are the average projects we have seen running for your organization and refresh that data each day, if you recently switched wait to see if you are still getting it tomorrow.
Assuming you have only set up activeState projects to run on this one system, you can use ps aux | grep activestate to try and get an idea of which other projects or instances you have running and can then stop those.
If you installed on more than one system (or it’s a public project and others my be using it) that could also be causing the warning.
Sorry for the confusion.
(i do wonder if the two different users could be contributing to the issue)
Hi Nicole,
Sorry for not replying sooner, I was away on vacation for several days. I can therefore safely say I haven’t used any state command (or anything else for that matter) in 5 days.
Unfortunately, I got the same warning message today when I ran “state pull” (it says my activestate.yaml is already up to date, but that’s beside the point). I rebooted, and got the same response.
This is on Windows 10 Pro. I used the Task Manager to search for ActiveState processes, and found state-svc.exe, from C:\Users\root\AppData\Local\ActiveState\StateTool\release\bin. I assume this is normal. In any case, I terminated this task and tried “state pull” again; I got the same warning.
I checked, and the other user didn’t have a state-svc task running. The other user doesn’t even have state installed anymore.
I didn’t install anything on any other system, and nobody else is using the project.
Is there a log file somewhere that would provide information on why state believes there’s more than one instance running?
I don’t mind uninstalling and reinstalling everything, if that has a reasonable chance of fixing the problem.
Thanks!
I have the same issue.
AciveState state has only ever been installed for one user on my computer. Over a few days prior to yesterday I removed a project and installed another several times, and ended up with none installed. Yesterday, whilst installing a new project (the only one associated with my account) I saw the heads up message ‘You are using 2 out of 1 available runtimes.’
Today, opening a Command Prompt in the project folder (containing the .yaml files), then running ‘state use’ or ‘state shell’ gives the heads up message ‘You are using 2 out of 1 available runtimes.’
I will check whether this is still the case in 24 hours or more.
I have one project for one user on Windows. As long as I can continue with that, I shall ignore the message. If I am prevented from continuing without upgrading, then (after 11 years of using ActiveState) I shall simply go elsewhere.
Until ActiveState assist further with resolving why I am seeing ‘can’t load dll’ during the compile phase when running a script (see Unusable Perl 5.36 build - compilation failures due to various dll files not loading), I have zero ActiveState projects in use.
So sorry it’s saying 2 when it ought to be one! Although it’s an annoying error it won’t actually block you, so if it’s only showing 1 state-svc.exe you should be just fine to ignore it and keep going. I’ll check in on our side to see if our daily re-calculations are running correctly or if there are any bugs.
You are correct it’s only a warning and won’t actually block you, it’s a kind of clean up reminder / warning so people do not hit a hard limit by installing and keeping active too many runtimes.
Thanks Nicole.
Let me know if you’d like copies of log files or anything like that. I’ll be happy to help.
Hi,
I just discovered there are two organizations in my account, gamin-mb and gamin-mb-org. Could this explain why state believes I have more than one runtime?
I don’t remember creating a second organization, should I remove one of the two?
Thanks
The -org one is an artefact of an older process to create new user organizations that we have since removed. The other one will be your permanent personal workspace/organization.
I notice that the warning is now saying you have 1 runtime, but it’s still warning that 1 < 1, which it isn’t.
If you want to remove the artefact organization, move your project to your permanent personal workspace, and send an email to support@activestate.com.
I notice that the warning is now saying you have 1 runtime, but it’s still warning that 1 < 1, which it isn’t.
At first, I thought you were talking about warnings appearing on my system, and wondered how you could know that. So I checked, and indeed, I no longer get the warning that I am using 2 runtimes when running commands such as ‘state pull’. So that issue seems to be fixed, even though I haven’t made any modification to my system.
But I think you were referring to the runtime usage listed on my organization page (gamin-mb-org) and, as you mentioned, it says I have “1 Concurrent Runtimes” and “This organization exceeds the usage limit of 1 concurrent runtimes for Free tier subscriptions”. Weird.
If you want to remove the artefact organization, move your project to your permanent personal workspace, and send an email to support@activestate.com
Okay. I read the documentation on how to move projects between organizations. It seems simple enough, but I wouldn’t have time right now to deal with potential permission issues or whatnot, so I’ll do it in a couple of weeks.
Thanks for your help!
How do I get rid of non-existing projects?
To remove the artefact organization, I moved my project to my permanent personal workspace using the instructions here: Moving your project :: ActiveState Platform Documentation.
Then, on my Windows installation, I had no valid project left (state pull said “The requested project Perl-5.36.0-Windows does not exist under gamin-mb-org”), so I checked out the moved project with state checkout gamin-mb/Perl-5.36.0-Windows --runtime-path c:/Perl. Now I have two projects, one of which (in gamin-mb-org) doesn’t exist:
Name Organization
──────────────────────────────────────────────────────
Perl-5.36.0-Windows gamin-mb
├─ Local Checkout → C:\Users\root\Perl-5.36.0-Windows\Perl-5.36.0-Windows
└─ Executables → c:\Perl\exec
Perl-5.36.0-Windows gamin-mb-org
├─ Local Checkout → C:\Users\root\Perl-5.36.0-Windows
└─ Executables → c:\Perl\exec
I had so many installation and configuration issues, I’m tempted to uninstall everything related to ActiveState from my computer (while keeping my project on the platform) and reinstall from scratch. Would the following do this?
uninstall Komodo (using standard Windows tools)
state clean uninstall
manually remove all references to ActiveState from system and user PATH variables
state-remote-installer.exe
state auth
state checkout gamin-mb/Perl-5.36.0-Windows --runtime-path c:/Perl
manually add C:\Perl\bin to the system PATH
install Komodo with Komodo-IDE-12.0.1-91869.msi
Thanks!
Run a “state clean cache” to make sure you don’t have a cached copy of the runtimes. However, it looks like you reused the same folder for the runtimes of two different projects from two separate orgs, and clean cache will remove that folder.
To remove a project from the projects report, remove the project folder. Even after a cache clean, the project folder is preserved.
Perl/bin is not what you need on PATH. Those are non-relocated because that’s a relocatable folder. The Perl/exec folder needs to be your first entry on PATH. The old bin folder and the old site/bin folder might be needed for compatibility with old code, and in some cases you might need to add the usr/lib folder as a workaround.
Wow, that’s very useful information, thanks!
My installation is for a home computer with more than one user, and I had tried “state checkout” for each user, which was not the way to go, until I discovered “state checkout --runtime-path”, but I couldn’t find information on how to make C:\Perl available to all users. Your post is the first bit of information I have to make this setup work properly, so please allow me to ask a few more questions…
-
What do you mean by “relocatable folder”?
I know about relocatable object libraries, but the executables under Perl/bin work fine for me.
In fact, Perl/exec isn’t even in the PATH of any user on my system. What’s the difference between the files in the exec folder and those n the bin folder?
-
When is “AppData\Local\activestate\cache\bin” necessary? Can I get rid of it?
Given that I want only one runtime on this system, to be installed with “state checkout --runtime-path” and shared by all users, I’m trying to keep my system clean.
-
Is the following the correct way to clean my system and start from scratch? (all done from the admin account except where noted)
state clean uninstall for each user on the system
delete AppData\Local\activestate for each user (in case state clean uninstall didn’t do it)
manually remove all references to ActiveState from system and user PATH variables
state-remote-installer.exe
state auth
state checkout gamin-mb/Perl-5.36.0-Windows --runtime-path C:/Perl
state clean cache (to remove cached runtimes, because the only one I want is in C:\Perl)
manually add these to the system PATH (in that order): C:\Perl\site\bin;C:\Perl\usr\bin;C:\Perl\exex
-
Is Komodo v12 sufficiently independent from the “state” command that I don’t need to worry about it when uninstalling/reinstalling Perl? (other than configuring the correct path for Perl in Komodo)
Thanks again. I know I’m asking a lot of detailed questions, but I’ve never had such a hard time installing Perl (and I’ve been doing it since Perl 4 
). I’m sure this documentation will be useful to someone else.