I have a worker dyno that I use to run my discord bot. It works normally every day and I have been using it for a long time but suddenly today is just stopped working even though it shows that it turned the dyno on but my bot is still offline and I also have enough hours so it is not a hours problem too(My code is also perfect which I have connected through GitHub pipeline). I cannot figure out what's wrong with the dyno. Does anybody know why it might be happening?
Solved. I was missing the ms module. So I installed the ms module using npm i ms -s and then updated my package.json file to Github and when the build was done, it worked.
Related
So I have been working on CRA and NextJS projects for the last 5-6 months and it works every time but since yesterday, I have no idea what has happened but every time I run my project I cannot access it at localhost:3000.
This message is displayed usually when a NextJS app starts -
started server on 0.0.0.0:3000, url: http://localhost:3000
Localhost gives me the following -
However when I go to 0.0.0.0:3000 , I'm able to access my application normally.
I have no idea what has happened,
My suspicion is the PHP live server extension in VS Code, I accidentally clicked on it and my localhost hasn't been working since. I have since uninstalled and removed PHP Live server extension, flushed my dns, cleared my cache but no changes yet.
I have tried multiple different projects and even a fresh CRA install to diagnose and the problem persists.
Any help would be greatly appreciated.
Thank you for your time.
I have been using Openshift 3 seamlessly to build and deploy a Node.js application for several months.
Since yesterday, new builds of the same app systematically fail because they are stuck forever in the Pending state, with the "Started status: not started" until after an hour when the build fails with "No logs available".
Has anyone else had this issue?
I am using starter-us-east-1 (no mention of it in status.starter.openshift.com).
My app runs fine locally and I don't understand what's the issue with Openshift.
Deployment of existing builds seems to work, but there's no way to make new builds, either manually or via webhooks.
I didn't change anything in the configuration, just my code.
Thank you by advance for any hint.
Additional info: The issue doesn't occur in starter-ca-central-1 where I can see a whole new interface with notifications, and the build of the app I have there works fine.
More info: The new interface has been rolled out to starter-us-east-1, but the problem is still more present than ever. Here is a screenshot of my Pods/Events tab:
This is a desperate cry for help. I am working on my finals exam and need a few tools to do this, mainly an SQL Server.
In short, I can't for whatever reason install SQL Server 2014 Express.
When installing, I just set up everything with its default values and settings and then let it perform the install, everything goes fine until it reaches the stage: SqlEngineDbStartConfigaction_install_configrc_cpu64 where it stop with an error. Details can be seen in this picture as well as error code and description: http://imgur.com/pq2BB6c
For the full error log just follow this link: http://pastebin.com/FfWeJi0i
I have tried literately everything I can think of, I edited permissions, registry, uninstalled reinstalled countless times, I updated windows several times, restarted countless times, I even went as far as to fully format my pc and start over.. however this too turned out to be a waste of time since the problem persists even after the reinstall of windows 7.
If I can't get this issue resolved I might not be able to finish my exam project, so consider me desperate.
One day, out of nothing, my app decided not to die.
After pressing ctrl + c when I inspect port it's still there and not only on my machine but also on server that is managed by PM2 so I need to go there each time and kill the process by hand. I tried to look for issues in my code and when I couldn't I just though that it's simply one of the dependencies fault and soon there will be a fix. It was slightly annoying but I could kill the process with kill -9 PID and I had most of the tasks I had on front-end side so it wasn't that big issue. Today, more than a week later problem it's still here.
I went back in history, picked a commit that I made weeks ago, where everything worked perfectly fine, switched NodeJS from 5.1.0 to 4.2.1, cleared npm cache, reinstalled all dependencies and I still see the problem.
I'm using LoopbackJS, but normally I start the app simply with "node server/server.js" and then the problem described above happens, but if I use "slc run" and then try to kill the app with ctrl + c it just hangs forever, I mean I can press ctrl+c as many times as I want and it's still running in console foreground.
If instead of pressing ctrl+c I kill the tab in console, app dies without problems.
This is what I see after running "lsof -i tcp:4000" when the app is supposed to be dead but is not
Edit:
Running and killing it with Strongloop process manager - slc start/slc stop works fine but it would be more convenient to use normal way of running NodeJS app (node server.js) during development and it doesn't change the fact that there is some issue and it would be better to not hide it under the carpet.
Out of anger I stripped out my app to the most basic elements. File by file, piece by piece and I found the answer.
The culprit was phantomJS - https://github.com/sgentle/phantomjs-node. PATCH version 0.8.2 introduced this bug. Fix was created almost a month ago, merged a week ago but not published on npm yet.
We have CRON jobs running on our app, all of which were working fine till last night. All the tasks (we have a few in minutely and hourly) have stopped abruptly (the last log entry was for around 1:52 AM IST).
Openshift seems to be running an upgrade since Nov 3, 12:46 EST, so I assume it is because of this but usually any issues during such events subscide within an hour.
We ahve tried the usual steps : Stop/Sart the CRON cartridge, Stop/Start the app, Removed the Cron cartridge and added again but its not working.
Anyone else facing this right now??
It seems I had to restart the app once more after after re-adding the cartridge. Now its working, although why it occurred is still a mystery.