Node.js variables are stuck on one machine
I have a Node.js app that waits for user input, then it requests the top trends from Twitter and sends the top 5 trends to discord. The API page Here.
I have that app running on a Ubuntu VPS along with other bots. The problem I have noticed has been ongoing for 3 days now. The bot is sending the same 5 tops trends again and again.
I have restarted the app but it still stuck on the same 5 trends. I have tested the app on my personal computer and it ran correctly. So I have searched for cache cleaning commands and I have tried ync; echo 1 > /proc/sys/vm/drop_caches. but it didn't work. I also have tried restating the VPS and the problem still persists. The app is in github so the version on my personal computer is the same as the VPS.
I checked the twitter API response on the VPS and the response is wrong, but I think that's the old response stuck in the memory as the app works perfectly on any other machine.
//Import the library
let Twitter = require('twitter');
//Enter Creditial
let client = new Twitter({
consumer_key: '',
consumer_secret: '',
access_token_key: '',
access_token_secret: ''
});
//Get the trends in the place of that ID
client.get('trends/place', {id: CountryID}, function(error, tweets, respond){
console.log(tweets[0].trends)
}
The tweets[0].trends is giving the same output for 3 days on the VPS. It works fine on any other computer, and the other bots are working fine. I don't know what's happening.
Edit:
The twitter response for my computer is for trends of today
as_of: ‘2019-01-01T16:17:20Z’,
created_at: ‘2019-01-01T16:15:31Z’,
But for some reason, my VPS gets the response from the 22nd and December.
as_of: ‘2019-01-01T16:16:06Z’,
created_at: ‘2018-12-22T23:47:54Z’
As I have mentioned. The same program is being run on both machines here.
node.js ubuntu twitter
asked Jan 1 at 15:39
ABDULAZIZ ALAHMADIABDULAZIZ ALAHMADI
75
add a comment |
I have a Node.js app that waits for user input, then it requests the top trends from Twitter and sends the top 5 trends to discord. The API page Here.
I have that app running on a Ubuntu VPS along with other bots. The problem I have noticed has been ongoing for 3 days now. The bot is sending the same 5 tops trends again and again.
I have restarted the app but it still stuck on the same 5 trends. I have tested the app on my personal computer and it ran correctly. So I have searched for cache cleaning commands and I have tried ync; echo 1 > /proc/sys/vm/drop_caches. but it didn't work. I also have tried restating the VPS and the problem still persists. The app is in github so the version on my personal computer is the same as the VPS.
I checked the twitter API response on the VPS and the response is wrong, but I think that's the old response stuck in the memory as the app works perfectly on any other machine.
//Import the library
let Twitter = require('twitter');
//Enter Creditial
let client = new Twitter({
consumer_key: '',
consumer_secret: '',
access_token_key: '',
access_token_secret: ''
});
//Get the trends in the place of that ID
client.get('trends/place', {id: CountryID}, function(error, tweets, respond){
console.log(tweets[0].trends)
}
The tweets[0].trends is giving the same output for 3 days on the VPS. It works fine on any other computer, and the other bots are working fine. I don't know what's happening.
Edit:
The twitter response for my computer is for trends of today
as_of: ‘2019-01-01T16:17:20Z’,
created_at: ‘2019-01-01T16:15:31Z’,
But for some reason, my VPS gets the response from the 22nd and December.
as_of: ‘2019-01-01T16:16:06Z’,
created_at: ‘2018-12-22T23:47:54Z’
As I have mentioned. The same program is being run on both machines here.
node.js ubuntu twitter
asked Jan 1 at 15:39
ABDULAZIZ ALAHMADIABDULAZIZ ALAHMADI
75
Interesting. Is your app running for 3 days straight, or does it work again if you restart it? Also, is the system time of the Ubuntu machine accurate?
– Elliot Nelson
Jan 1 at 17:38
add a comment |
I have a Node.js app that waits for user input, then it requests the top trends from Twitter and sends the top 5 trends to discord. The API page Here.
I have that app running on a Ubuntu VPS along with other bots. The problem I have noticed has been ongoing for 3 days now. The bot is sending the same 5 tops trends again and again.
I have restarted the app but it still stuck on the same 5 trends. I have tested the app on my personal computer and it ran correctly. So I have searched for cache cleaning commands and I have tried ync; echo 1 > /proc/sys/vm/drop_caches. but it didn't work. I also have tried restating the VPS and the problem still persists. The app is in github so the version on my personal computer is the same as the VPS.
I checked the twitter API response on the VPS and the response is wrong, but I think that's the old response stuck in the memory as the app works perfectly on any other machine.
//Import the library
let Twitter = require('twitter');
//Enter Creditial
let client = new Twitter({
consumer_key: '',
consumer_secret: '',
access_token_key: '',
access_token_secret: ''
});
//Get the trends in the place of that ID
client.get('trends/place', {id: CountryID}, function(error, tweets, respond){
console.log(tweets[0].trends)
}
The tweets[0].trends is giving the same output for 3 days on the VPS. It works fine on any other computer, and the other bots are working fine. I don't know what's happening.
Edit:
The twitter response for my computer is for trends of today
as_of: ‘2019-01-01T16:17:20Z’,
created_at: ‘2019-01-01T16:15:31Z’,
But for some reason, my VPS gets the response from the 22nd and December.
as_of: ‘2019-01-01T16:16:06Z’,
created_at: ‘2018-12-22T23:47:54Z’
As I have mentioned. The same program is being run on both machines here.
node.js ubuntu twitter
asked Jan 1 at 15:39
ABDULAZIZ ALAHMADIABDULAZIZ ALAHMADI
75
I have a Node.js app that waits for user input, then it requests the top trends from Twitter and sends the top 5 trends to discord. The API page Here.
I have that app running on a Ubuntu VPS along with other bots. The problem I have noticed has been ongoing for 3 days now. The bot is sending the same 5 tops trends again and again.
I have restarted the app but it still stuck on the same 5 trends. I have tested the app on my personal computer and it ran correctly. So I have searched for cache cleaning commands and I have tried ync; echo 1 > /proc/sys/vm/drop_caches. but it didn't work. I also have tried restating the VPS and the problem still persists. The app is in github so the version on my personal computer is the same as the VPS.
I checked the twitter API response on the VPS and the response is wrong, but I think that's the old response stuck in the memory as the app works perfectly on any other machine.
//Import the library
let Twitter = require('twitter');
//Enter Creditial
let client = new Twitter({
consumer_key: '',
consumer_secret: '',
access_token_key: '',
access_token_secret: ''
});
//Get the trends in the place of that ID
client.get('trends/place', {id: CountryID}, function(error, tweets, respond){
console.log(tweets[0].trends)
}
The tweets[0].trends is giving the same output for 3 days on the VPS. It works fine on any other computer, and the other bots are working fine. I don't know what's happening.
Edit:
The twitter response for my computer is for trends of today
as_of: ‘2019-01-01T16:17:20Z’,
created_at: ‘2019-01-01T16:15:31Z’,
But for some reason, my VPS gets the response from the 22nd and December.
as_of: ‘2019-01-01T16:16:06Z’,
created_at: ‘2018-12-22T23:47:54Z’
As I have mentioned. The same program is being run on both machines here.
node.js ubuntu twitter
node.js ubuntu twitter
asked Jan 1 at 15:39
ABDULAZIZ ALAHMADIABDULAZIZ ALAHMADI
75
asked Jan 1 at 15:39
ABDULAZIZ ALAHMADIABDULAZIZ ALAHMADI
75
edited Jan 1 at 16:37
ABDULAZIZ ALAHMADI
asked Jan 1 at 15:39
ABDULAZIZ ALAHMADIABDULAZIZ ALAHMADI
75
asked Jan 1 at 15:39
ABDULAZIZ ALAHMADIABDULAZIZ ALAHMADI
75
asked Jan 1 at 15:39
ABDULAZIZ ALAHMADIABDULAZIZ ALAHMADI
75
75
Interesting. Is your app running for 3 days straight, or does it work again if you restart it? Also, is the system time of the Ubuntu machine accurate?
– Elliot Nelson
Jan 1 at 17:38
add a comment |
Interesting. Is your app running for 3 days straight, or does it work again if you restart it? Also, is the system time of the Ubuntu machine accurate?
– Elliot Nelson
Jan 1 at 17:38
Interesting. Is your app running for 3 days straight, or does it work again if you restart it? Also, is the system time of the Ubuntu machine accurate?
– Elliot Nelson
Jan 1 at 17:38
Interesting. Is your app running for 3 days straight, or does it work again if you restart it? Also, is the system time of the Ubuntu machine accurate?
– Elliot Nelson
Jan 1 at 17:38
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53996743%2fnode-js-variables-are-stuck-on-one-machine%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53996743%2fnode-js-variables-are-stuck-on-one-machine%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Interesting. Is your app running for 3 days straight, or does it work again if you restart it? Also, is the system time of the Ubuntu machine accurate?
– Elliot Nelson
Jan 1 at 17:38