I have shiny running on a mac. These apps have previously been working. I'm getting the following error when I try to access any of them
The application failed to start.
The application exited during initialization.
su: illegal option -- p
usage: su [-] [-flm] [login [args]]
This is also all that is in the log. Any ideas on what is going on here? I know shiny server is not intended for mac which is why we are transitioning to a linux server, but in the meantime I need these apps which were previously working to continue working.
Related
I've recently been developing an app, and noticed a few days ago I updated R to 4.1.2. After making some changes to the app, I used the Publish button to deploy to shinyapps.io. The deployment console threw the following error and failed:
Error: Unhandled Exception: Child Task 1045191965 failed: Error building image: R version 4.1.2 currently unavailable
Execution halted
Now, I've deployed many times previously, and this was the first deployment since the update to R. I haven't included any code because my app.R is over 1500 lines and it really didn't seem to be related to any of thee changes I made. I was wondering if anyone could help me figure out whether this error is referring to my system or the server I am deploying to. I expect I may have to roll back to the pre-update snapshot and try again, but I'd like to avoid doing that if the problem lies somewhere else.
Rstudio is Version 1.4.1103
Operating system:
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
Thanks in advance!
After checking with shinapps.io support, they informed me their server has not been updated to 4.1.2 and to downgrade until they are able to make the upgrade. They were not able to provide an ETA on that. Thanks to the support staff there!
This question already has an answer here:
Error: Discard position id too big
(1 answer)
Closed 4 years ago.
I have a running shiny app on a web server that worked fine until I would say last week. Now, on occasion (I guess every two days) the app stops working with the "Application failed to start" message. When I restart the shiny server, as I did just now, everything runs fine again.
https://butterlab.imb-mainz.de/flydev/
The funny thing is, I have other apps on this server as well, and they are not affected and run fine in parallel, even if this app failed.
I can not find any error message in the log files. And I am wondering: how I could debug this, since the app is now running fine?
Looking forward to any advice.
EDIT:
I checked the shiny-server.log file after the error occurred and I found the following message:
[2018-06-14 14:29:20.080] [WARN] shiny-server - RobustSockJS collision: MqU4rgur76RPgjJIPr
[2018-06-15 01:28:18.398] [WARN] shiny-server - Error handling message: Error: Discard position id too big
[2018-06-15 02:00:10.358] [INFO] shiny-server - Error getting worker: Error: The application took too long to respond.
[2018-06-15 02:00:10.364] [INFO] shiny-server - Error getting worker: Error: The application took too long to respond.
The last message gets repeated whenever someone accesses the server.
So in the end, it seems this page solved my problem Error: Discard position id too big
I set app_init_timeout and app_idle_timeout both to 1800and since then I have no further problems.
Also the comment with the restart.txt file might be interesting. I thought about testing with a shell script if the page is still working, otherwise touching the txt.
http://docs.rstudio.com/shiny-server/#restarting-an-application
But as I said, in the end it works by adjusting the app_init_timeout and app_idle_timeout.
I am loading one of the example apps from Shiny R into ShiniApps.io`
library(shinyapps)
shinyapps::setAccountInfo(name='xxx', token='xxx', secret='xxx')
deployApp("01_hello")
and then I get this error:
Error: Unhandled Exception: 'NoneType' object has no attribute 'getitem'
The app appeared in the web-page of Shinyapps.io as "undeployed".
Any clue what may be causing this error? the error is the same whether I run R 64 or 32 bit.
I had the same problem today. I wasn't able to successfully deploy a new app (getting the same error), but I was able to redeploy a previous app.
I have tried removing all packages and code from my new app (left only empty shinyServer and shinyUI functions uncommented) and still couldn't deploy.
Restarted R several times. Updated all packages. Nothing helped.
A few hours later I tried to deploy again and it passed without errors.
I know this is not exactly an answer but I suspect it was a server-side error because it failed during the "Starting instances" step of deployment.
So try to deploy it again, hope it works this time.
Fresh install of Meteor 0.5.0 on Windows Vista. I don't get the basic examples working. No success after creating the empty'ish hello app either. The shell is running as admin. Meteor recognises that I changed a source file, but then nothing. It doesn't matter where in the filesystem i try this. Always getting
Exited with code: -1073741819:
eg
C:\Users\jawford\Meteor Apps\Examples>meteor create starter3
starter3: created.
To run your new app:
cd starter3
meteor
C:\Users\jawford\Meteor Apps\Examples>cd starter3
C:\Users\jawford\Meteor Apps\Examples\starter3>meteor
[[[[[ C:\Users\jawford\Meteor Apps\Examples\starter3 ]]]]]
Running on: http://localhost:3000/
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
=> Modified -- restarting.
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
^CTerminate batch job (Y/N)? y
C:\Users\jawford\Meteor Apps\Examples\starter3>
If you run into this problem using Windows 8, you will need to change compatibility mode for the node executable.
Go to the folder where you installed Meteor
Open properties for bin/node.exe
Set compatibility mode for Windows 7
You should now be able to start the application as you did earlier.
This has to do with Fibers not loading correctly. You can attempt to run app/meteor/meteor.js with bin/node, both are in the Meteor directory in Program Files. This could maybe give you more details why it is crashing. It might also be handy to run the tests in the lib/node_modules/fibers folder which might point out why Fibers is misbehaving.
The exit code -1073741819 corresponds to C0000005 which indicates an access violation.
Many users find that setting compatibility mode to "Windows 7" solves that problem, but it doesn't always and there is some evidence that it also occurs on Windows 7.
Investigating a later issue on win Meteor 0.5.9, I discovered a problem with fibers on windows that may explain this issue, and I have a tentative fix.
Please see: https://github.com/TomWij/meteor/issues/66#issuecomment-15994548 for further details.
Recently when trying to run ASP.net Web Applications, I started receiving an error of:
"Attaching the ProteusDebugEngine debugger to process '[9352] WebDev.WebServer40.exe' on machine 'PC' failed. Invalid pointer”
“OK”
And when I click “ok” I got this message:
“Unable to start program 'http://localhost:8888/Welcome.htm' . Element not fount”
I am not really sure what changed on my pc. Any ideas???
Thanks
Running the following in the Visual Studio Command Prompt (2010) solved this for me.
devenv /resetskippkgs