had a problem when I was trying to deploy my django app with EB. I got something like this:
Instance has not sent any data since launch
each time I change options etc. The AWS in refers me to check my eb-engine.log file in which there is one error line:
[ERROR] An error occurred during execution of command [app-deploy] - [StageApplication]. Stop running the command. Error: staging application failed due to invalid zip file `
Moreover I consistently see in my 'Health section' app's environment 'No data'.
I've uploaded file with .zip extension as it is written. I checked my configuration file before as well as tried to change instance (to have more memory) and nothing worked. I'm pretty new in AWS and don't have really a clue how I can deal with that.
Related
I am running a python shell program in AWS Glue but after running for around 10 minutes its failing with error Internal service error. The logs or error logs does not give any information. Most of the time it fails by just saying Internal service error and rarely it runs for 2 days and gets timed out. The code uses pandas for transformations and it looks ok, it runs fine on local machine, necessary changes done so that it works on AWS glue[where it read/write files to s3 location instead of local folder]. What could be wrong here? Any input is appreciated.
This issue was figured out. The problem was the job was unable to download the dependent python libraries due to an access issue to the s3 bucket. Once the access issue was resolved the job started running fine.
The error you can see file not foundFile not found an error on GitLab when converted to large file system LFS. The file is present on GitLab server and I can download it is perfect. But when I tried to run make a test on the GitLab server it gives me such an error.
Sorry, I'm new to this, I am sorry if I could not frame the question in a proper format.
The file is present in the repository and it opened and works fine when downloaded, only the make test does not run on server. Make test runs fine on local machine. I think it is something related to LFS. Idk but
Link to error on gitlab
Link to file which is present but still error occurs
Following this guide I created a service from a python script and used "py [script name] install". The service was installed successfully and I can see it in the services window. If I run the service through the command line using "py [script name] start", it all works correctly.
However, when I try to start it from the Windows Services window, it gives a different error depending on the account I use. All of these are suggestions I've seen on various forums:
1) Default (Local System Account)
When I try this one, it gives error "Windows could not start the service on Local Computer."
2) The admin account, which I'm running the cmd from
Same error as above
3) LOCAL SERVICE
Gives "Error 5: Access is denied." even though I'm logged in as admin.
Does anyone know what could be causing this?
I also tried creating a .exe from the python script and adding that as a service using sc.exe. However, when I did that, I never got past "The service did not respond to the start or control request in a timely fashion." This error also occurred when running it from the CMD until I copied some files into a directory in the python installation.
I've never tried a python script as a service, so I can't speak to that directly.
I do know that the "The service did not respond to the start or control request in a timely fashion." error is almost always an indication that the OnStart() callback to the service (looks like SvcDoRun in your case) starts a long running operation (e.g., while loop) that never returns. The OnStart() callback is expected to kick off a foreground thread that will keep the service running and then return. From my recollection, if OnStart() doesn't return in about 30 seconds or so, Windows kills the service as unresponsive, which trigger this particular error message.
Another thing to look at is the event viewer. It may be that your service is throwing an exception that you're not seeing due to process isolation.
I have a flask app that creates a sqlite db to load fixtures for tests. When I run pytest within osx, there are no issues. However, when I set 'PRAGMA journal_mode=WAL' within a ubuntu 14.04 docker container, I get this:
disk I/O error
Traceback (most recent call last):
File "/tmp/my_app/util/sqlalchemy_helpers.py", line 23, in pragma_journalmode_wal
cursor.execute('PRAGMA journal_mode=WAL')
OperationalError: disk I/O error
The sqlite db file is written to a folder within tmp that is dynamically created using python's "tempfile.mkdtemp" function. Even though the tests run as root (because docker), I still made sure the folder has full read/write/execute permissions. I verified that there is plenty of space left on /tmp. I have test code that creates, modifies, and deletes a file in the database folder, and it passes successfully.
I cannot seem to find a way to get an error code or better explanation as to what failed. Any ideas how I can better debug the issue? Could there be an issue with the docker container?
I had similar problem right now, when recreating sqlite3 database:
Removed database.sqlite3
Created database.sqlite3
Setup right permissions.
Error ocurred.
After some titme figured out that I have also database.sqlite3-shm and database.sqlite3-wal
Removed database.sqlite3-shm and database.sqlite3-wal
And everything goes back to normal.
I am compiling a website using TeamCity on a server and need to deploy the compiled website to AWS.
As my last build step, I use the Elastic Beanstalk CLI to deploy: "C:\Python34...\eb.exe deploy".
eb init has already been run...but whenever I run "eb deploy", (even when I run it from the command line in an empty directory--which should deploy a default project to AWS), an error appears saying:
Error: PermissionError :: [Errno 13] Permission denied: './pagefile.sys'
I have already run the command on my local machine without any problems; I receive the error on the server regardless of whether I am running the command line as an administrator.
I am wondering if this is a permissions issue with the server, or something else? I haven't been able to achieve much insight from the other questions, because they seem to have been solved on a case-by-case basis.
pagefile.sys is the Windows swap file.
It is a special file which cannot be written or manipulated. Whatever your command is doing you need to fix your command so it that doesn't touch this file and ignores it.