Attempt to upgrade AWS Parse Server from Parse 2.6.1 to current ending in package.json error

happssoftware 2018-04-03 02:28:00 UTC #3

Thank you so much!! These steps resolved my issue and my Parse Server has been updated.

crhernandez 2018-04-03 07:46:53 UTC #4

Hi,

We are glad that you were able to fix the issue. We will update this thread as soon as we have more news about the fix for future versions.
If you have any other questions, please do not hesitate to let us know.

Best regards,
Carlos R. Hernández

nehloo 2018-09-02 07:14:11 UTC #5

Hi Carlos,

I'm still at parse server 2.2.22 and parse dashboard 1.0.18 (don't ask).

After I run npm update -g npm I get this error:

/opt/bitnami/nodejs/lib/node_modules/npm/bin/npm-cli.js:85
let notifier = require('update-notifier')
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode

Then I get all sorts of errors about npm:

You'll need to upgrade to a newer version in order to use this version of npm. Supported versions are 6, 8, 9, 10, 11. You can find the latest version at https://nodejs.org/

How can I update to latest server and dashboard from the old... 2.2.22?

Thanks!

jota 2018-09-03 10:53:34 UTC #6

Hi @nehloo,

Our team is reviewing this information and will update this thread as soon as we have more information.

Thanks

crhernandez 2018-09-04 07:32:34 UTC #7

Hi,

What versions of node and npm are you using? You can obtain it by running

node -v
npm -v

Best regards,
Carlos R. Hernández

nehloo 2018-09-04 13:03:21 UTC #8

Hi Carlos,
node v4.5.0
npm 4.0.3

crhernandez 2018-09-07 08:34:51 UTC #9

Hi,

It seems that you're using old versions for node and npm, can you upgrade both?
From your previous message, you are trying to update npm unsuccessfully, you should update node first.

You can use Node Version Manager (NVM). It's a Bash script that lets you download and manage different versions of node.
At this moment, Node LTS is 8.11.4, but you can use other branches. Once you have a proper node version on your system, can you try to upgrade npm by running npm update -g npm?

Please let us know if this solves the issue.

Best regards,
Carlos R. Hernández

nehloo 2018-09-16 01:13:40 UTC #10

Carlos,

I upgraded Node to v10 and then to v8.12.0.
Npm is now 6.4.1.

But I'm getting this recurring/infinite error when I run "npm install parse-server parse-dashboard"... thoughts? Thanks!

/home/bitnami/BACKUP# npm install parse-server parse-dashboard
npm WARN deprecated uws@10.148.1: stop using this version

bcrypt@3.0.0 install /home/bitnami/node_modules/bcrypt
node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Pre-built binaries not installable for bcrypt@3.0.0 and node@4.5.0 (node-v46 ABI, glibc) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error EACCES: permission denied, mkdir '/home/bitnami/node_modules/bcrypt/lib'
gyp info it worked if it ends with ok
gyp verb cli [ '/opt/bitnami/nodejs/bin/.node.bin',
gyp verb cli '/opt/bitnami/nodejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli 'clean' ]
gyp info using node-gyp@3.4.0
gyp info using node@4.5.0 | linux | x64
gyp verb command clean []
gyp verb clean removing "build" directory
gyp info ok
gyp info it worked if it ends with ok
gyp verb cli [ '/opt/bitnami/nodejs/bin/.node.bin',
gyp verb cli '/opt/bitnami/nodejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli 'configure',
gyp verb cli '--fallback-to-build',
gyp verb cli '--module=/home/bitnami/node_modules/bcrypt/lib/binding/bcrypt_lib.node',
gyp verb cli '--module_name=bcrypt_lib',
gyp verb cli '--module_path=/home/bitnami/node_modules/bcrypt/lib/binding',
gyp verb cli '--node_abi_napi=node-v46' ]
gyp info using node-gyp@3.4.0
gyp info using node@4.5.0 | linux | x64
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb which succeeded python2 /usr/bin/python2
gyp verb check python version /usr/bin/python2 -c "import platform; print(platform.python_version());" returned: "2.7.6\n"
gyp verb get node dir no --target version specified, falling back to host node version: 4.5.0
> gyp verb command install [ '4.5.0' ]
> gyp verb install input version string "4.5.0"
> gyp verb install installing version: 4.5.0
> gyp verb install --ensure was passed, so won't reinstall if already installed
> gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/4.5.0"
> gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/bitnami/node_modules/bcrypt/.node-gyp"
> gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '4.5.0' ]
gyp verb install input version string "4.5.0"
gyp verb install installing version: 4.5.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 4.5.0
gyp verb ensuring nodedir is created /home/bitnami/node_modules/bcrypt/.node-gyp/4.5.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/home/bitnami/node_modules/bcrypt/.node-gyp/4.5.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/bitnami/node_modules/bcrypt/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '4.5.0' ]
gyp verb install input version string "4.5.0"
gyp verb install installing version: 4.5.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 4.5.0
gyp verb ensuring nodedir is created /home/bitnami/node_modules/bcrypt/.node-gyp/4.5.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/home/bitnami/node_modules/bcrypt/.node-gyp/4.5.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/bitnami/node_modules/bcrypt/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '4.5.0' ]

nehloo 2018-09-16 01:54:00 UTC #11

Carlos,

I was able to install it with --unsafe-perm... BUT now I cannot start the server... just keeping you guys updated:

/opt/bitnami/ctlscript.sh restart parse
error: Forever cannot find process with id: server.js
/opt/bitnami/apps/parse/scripts/ctl.sh : parse could not be stopped

Upgrade cmd:
/opt/bitnami/apps/parse/htdocs# npm install parse-server parse-dashboard --unsafe-perm

parse-server@3.0.0 postinstall /opt/bitnami/apps/parse/htdocs/node_modules/parse-server
node -p 'require("./postinstall.js")()'

              1111111111
           1111111111111111
        1111111111111111111111
      11111111111111111111111111
    111111111111111       11111111
   1111111111111             111111
  1111111111111   111111111   111111
  111111111111   11111111111   111111
 1111111111111   11111111111   111111
 1111111111111   1111111111    111111
 1111111111111111111111111    1111111
 11111111                    11111111
  111111         1111111111111111111
  11111   11111  111111111111111111
   11111         11111111111111111
    111111     111111111111111111
      11111111111111111111111111
        1111111111111111111111
          111111111111111111
              11111111111


    Thanks for installing parse 🙏

Please consider donating to our open collective
to help us maintain this package.

https://opencollective.com/parse-server

[ ......] | postinstall: sill lifecycle parse-server@3.0.0~postinstnpm WARN saveError ENOENT: no such file or directory, open '/opt/bitnami/apps/parse/htdocs/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/opt/bitnami/apps/parse/htdocs/package.json'
npm WARN htdocs No description
npm WARN htdocs No repository field.
npm WARN htdocs No README data
npm WARN htdocs No license field.

parse-dashboard@1.2.0
parse-server@3.0.0
updated 2 packages and audited 3833 packages in 6.517s
found 159 vulnerabilities (70 low, 45 moderate, 44 high)
run npm audit fix to fix them, or npm audit for details

nehloo 2018-09-16 02:35:59 UTC #12

Restarted the server via AWS... but now:

/opt/bitnami/ctlscript.sh restart parse
/opt/bitnami/apps/parse/scripts/ctl.sh : parse not running
warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: server.js
/opt/bitnami/apps/parse/scripts/ctl.sh : parse could not be started

nehloo 2018-09-16 05:42:31 UTC #13

Also... sudo tar -pczvf application-backup.tar.gz /opt/bitnami ... apparently did not backup the latest database... after I restored it, it only showed the data stored until Sep 2nd (not today Sep 16th).

nehloo 2018-09-16 15:54:24 UTC #14

After upgrades, my Parse Server now shuts down by itself, minutes after it starts successfully. Can someone please help advise? Thanks.

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

Parse Server 3.0.0 on Bitnami AWS instance
Parse Dashboard 1.2.0
Mongodb v3.0.9
node v10.10.0
npm 6.4.1

nehloo 2018-09-17 05:15:44 UTC #15

@crhernandez I was able to upgrade to latest versions. Then I tried to start the server, but it doesn't work unless I start it with "node /opt/bitnami/apps/parse/htdocs/server.js". Can you please advise?

Attempting to start normally via "server.js" doesn't work:

bitnami@ip:~$ sudo /opt/bitnami/ctlscript.sh restart parse

/opt/bitnami/apps/parse/scripts/ctl.sh : parse not running
warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: server.js
/opt/bitnami/apps/parse/scripts/ctl.sh : parse could not be started

This command returns the actual error, but what does it mean?

bitnami@ip:~$ sudo HOME=/opt/bitnami/apps/parse NODE_ENV=production /opt/bitnami/nodejs/bin/node /opt/bitnami/apps/parse/htdocs/server.js

/opt/bitnami/apps/parse/htdocs/node_modules/parse-server/lib/ParseServer.js:127
    const {
          ^

SyntaxError: Unexpected token {
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/opt/bitnami/apps/parse/htdocs/node_modules/parse-server/lib/index.js:8:21)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)

And here, the server actually starts, using the very same "server.js" file as the one used above, called directly with node... But I can't keep this my Terminal running this command forever...

bitnami@ip:~$ node /opt/bitnami/apps/parse/htdocs/server.js

(node:16103) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
(node:16103) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
verbose: REQUEST for [GET] /parse/config: {} method=GET, url=/parse/config, host=127.0.0.1:1338, content-type=text/plain, origin=..............

OR

bitnami@ip:~$ node /opt/bitnami/nodejs/bin/forever /opt/bitnami/apps/parse/htdocs/server.js

warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
(node:16156) ExperimentalWarning: The http2 module is an experimental API.
(node:16156) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
(node:16156) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.

Thanks!

crhernandez 2018-09-17 10:05:49 UTC #16

Hi,

Thanks for the detailed explanation. We have a Support Tool that will gather relevant information for us to debug the issue. Could you please download and execute it on the machine where the stack is running by following the steps described in the guide below? You must click on the platform or cloud that you are using to find the correct instructions.

How to Run the Bitnami Support Tool

Please note that you need to paste the code outputted by the tool in your reply.

Using the previous tool we can take a look at the logs and other relevant files in order to see what is happening when you try to start the service running ctlscript.sh.
In the meantime, if you add the & sign at the end of a command, you can run the process directly from the background:

node /opt/bitnami/apps/parse/htdocs/server.js &

Best regards,
Carlos R. Hernández

nehloo 2018-10-13 21:28:43 UTC #17

Hi Carlos,

The code is: 15115517-618a-4e36-dac5-b3da0c716a3b

I look forward to your findings.

Thanks!

Nelu

nehloo 2018-10-14 01:08:06 UTC #18

I'm also getting these errors, fyi:

/opt/bitnami/apps/parse/scripts/ctl.sh: 18: [: 3894: unexpected operator

(node:1634) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.

nehloo 2018-10-20 23:36:58 UTC #19

My .forever permissions are set like the following:

drwxr-xr-x 4 **daemon**  daemon 4.0K Oct 14 01:22 .forever

...instead of...

drwxr-xr-x 4 **bitnami**  daemon 4.0K Oct 14 01:22 .forever

Think this would be the issue? Should I chown -R bitnami:daemon .forever?

crhernandez 2018-10-23 08:53:53 UTC #20

Hi,

About your first message:

(node:1634) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.

This is a warning for future versions, it shouldn't affect us at this moment. But regarding the other issue

/opt/bitnami/apps/parse/scripts/ctl.sh: 18: [: 3894: unexpected operator

it seems a wrong operator on line 18 of /opt/bitnami/apps/parse/scripts/ctl.sh file, did you modify it? Anycase, this line should be

if [ $PARSE_PID ] ; then

Can you check if it has this value at this moment? If not, you can edit it running sudo YOUR_TEXT_EDITOR /opt/bitnami/apps/parse/scripts/ctl.sh.

About forever, where are you looking for? In a fresh instance:

ls -la /opt/bitnami/nodejs/bin/forever
lrwxrwxrwx 1 root root 39 Oct 18 14:02 /opt/bitnami/nodejs/bin/forever -> ../lib/node_modules/forever/bin/forever

ls -la /opt/bitnami/nodejs/lib/node_modules/forever/bin/forever
-rwxr-xr-x 1 root root 60 Nov  2  2016 /opt/bitnami/nodejs/lib/node_modules/forever/bin/forever

Please let us know if this solves the issue.

Best regards,
Carlos R. Hernández

nehloo 2018-12-22 16:23:23 UTC #21

Carlos,

Still it is not persistent... I am still enforcing the process to hang up, by launching it with "server.js &"...

For your latest suggestions, this is what my server returns:

bitnami@ip:~$ ls -la /opt/bitnami/nodejs/bin/forever
lrwxrwxrwx 1 root root 39 Oct 21  2016 /opt/bitnami/nodejs/bin/forever -> ../lib/node_modules/forever/bin/forever

bitnami@ip:~$ ls -la /opt/bitnami/nodejs/lib/node_modules/forever/bin/forever
-rwxr-xr-x 1 root root 60 Jun  8  2015 /opt/bitnami/nodejs/lib/node_modules/forever/bin/forever

The file "ctl.sh" already has this following line, I see nothing wrong there:

if [ $PARSE_PID ] ; then

I'm not sure what exactly is wrong. Any other thoughts?

Do you think I should do a fresh reinstall? How can I do this safely, without losing the database data?

Thank you!

crhernandez 2019-01-08 11:41:33 UTC #22

Hi,
About the issue with /opt/bitnami/apps/parse/scripts/ctl.sh, I am copying here the whole file present in a fresh instance, can you replace the one existing in your machine by this one?

#!/bin/sh

if [ `id|sed -e s/uid=//g -e s/\(.*//g` -eq 0 ]; then
    PARSE_START="env VERBOSE=1 HOME=/opt/bitnami/apps/parse NODE_ENV=production /opt/bitnami/nodejs/bin/node /opt/bitnami/nodejs/bin/forever start -l /opt/bitnami/apps/parse/htdocs/logs/parse.log --append server.js"
    PARSE_STOP="env VERBOSE=1 HOME=/opt/bitnami/apps/parse NODE_ENV=production /opt/bitnami/nodejs/bin/node /opt/bitnami/nodejs/bin/forever stop -l /opt/bitnami/apps/parse/htdocs/logs/parse.log --append server.js"
else
    PARSE_START="env VERBOSE=1 /opt/bitnami/nodejs/bin/node /opt/bitnami/nodejs/bin/forever start -l /opt/bitnami/apps/parse/htdocs/logs/parse.log --append server.js"
    PARSE_STOP="env VERBOSE=1 /opt/bitnami/nodejs/bin/node /opt/bitnami/nodejs/bin/forever stop -l /opt/bitnami/apps/parse/htdocs/logs/parse.log --append server.js"
fi

PARSE_PROGRAM="/opt/bitnami/apps/parse/htdocs/server.js"
PARSE_PID=""
PARSE_STATUS=""
ERROR=0

is_service_running() {
    PARSE_PID=`COLUMNS=400 ps ax | grep "$1" | grep -v "grep" | awk '{print $1}' 2>&1`
    if [ $PARSE_PID ] ; then
        RUNNING=1
    else
        RUNNING=0
    fi
    return $RUNNING
}

is_parse_running() {
    is_service_running "$PARSE_PROGRAM"
    RUNNING=$?
    if [ $RUNNING -eq 0 ]; then
        PARSE_STATUS="parse not running"
    else
        PARSE_STATUS="parse already running"
    fi
    return $RUNNING
}

start_parse() {
    is_parse_running
    RUNNING=$?
    if [ $RUNNING -eq 1  ]; then
        echo "$0 $ARG: parse (pid $PARSE_PID) already running"
        exit
    else
	    cd /opt/bitnami/apps/parse/htdocs
	    if [ `id|sed -e s/uid=//g -e s/\(.*//g` -eq 0 ]; then
            su daemon -s /bin/sh -c "$PARSE_START"
	    else
            $PARSE_START
        fi
    fi

    COUNTER=20
    while [ $RUNNING -eq 0 ] && [ $COUNTER -ne 0 ]; do
        COUNTER=`expr $COUNTER - 1`
        sleep 1
        is_parse_running
        RUNNING=$?
    done

    if [ $RUNNING -eq 0 ]; then
        ERROR=1
    fi
    if [ $ERROR -eq 0 ]; then
	    echo "$0 $ARG: Parse started"
    else
	    echo "$0 $ARG: parse could not be started"
	    ERROR=3
    fi

}

stop_parse() {
    NO_EXIT_ON_ERROR=$1
    is_parse_running
    RUNNING=$?
    if [ $RUNNING -eq 0 ]; then
        echo "$0 $ARG: $PARSE_STATUS"
        if [ "x$NO_EXIT_ON_ERROR" != "xno_exit" ]; then
            exit
        else
            return
        fi
    fi

    cd /opt/bitnami/apps/parse/htdocs
    if [ `id|sed -e s/uid=//g -e s/\(.*//g` -eq 0 ]; then
        su daemon -s /bin/sh -c "$PARSE_STOP"
    else
        $PARSE_STOP
    fi

    COUNTER=20
    while [ $RUNNING -eq 1 ] && [ $COUNTER -ne 0 ]; do
        COUNTER=`expr $COUNTER - 1`
        sleep 1
        is_parse_running
        RUNNING=$?
    done

    if [ $RUNNING -eq 0 ]; then
            echo "$0 $ARG: parse stopped"
        else
            echo "$0 $ARG: parse could not be stopped"
            ERROR=4
    fi
}



if [ "x$1" = "xstart" ]; then
    start_parse
elif [ "x$1" = "xstop" ]; then
    stop_parse
elif [ "x$1" = "xstatus" ]; then
    is_parse_running
    echo "$PARSE_STATUS"
fi

exit $ERROR

In this message you are talking about some .forever permissions that are different from the ones in /opt/bitnami/nodejs/bin/forever and /opt/bitnami/nodejs/lib/node_modules/forever/bin/forever. Where are those .forever files? The other ones seems to be properly configured.

About the reinstall, there is an easy way to migrate the application because the Bitnami Parse Server Stack is self-contained and the simplest option for performing a backup is to copy or compress the Bitnami stack installation directory but in this case, it seems that the data of this installation directory is corrupted so you can create a database backup in the existing server, move it to your local machine and restore the data in the new one, you can follow this guide https://docs.bitnami.com/aws/apps/parse/administration/backup-restore-mongodb/

Best regards,
Carlos R. Hernández

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!