PufferPanel Installation Error

Status
This thread has been locked.

Jayson

Supreme
Feedback score
17
Posts
1,258
Reactions
741
Resources
0
Greetings IT geeks of MC-Market. While installing PufferPanel on one of my VPS client's servers, I came up with the error of "An error occured while trying to connect to the remote node. Please check that Scales is running and try again." while creating a new server. I manually installed PufferPanel and Scales. Running on ubuntu 14.04 x86_64. For testing purposes, I opened all ports and Scales does have a successful start message. MySQL works fine.

No i'm not paying
 
Last edited:
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.

Jayson

Supreme
Feedback score
17
Posts
1,258
Reactions
741
Resources
0
Then try this:

Code:
cd /srv/scales

sudo npm start
Already tried earlier, and i'm on the root account.[DOUBLEPOST=1481774654][/DOUBLEPOST]I restarted scales and now the error has changed to this...
Sketch.png
 

Attachments

  • Sketch.png
    Sketch.png
    210.6 KB · Views: 221
Last edited:

Jayson

Supreme
Feedback score
17
Posts
1,258
Reactions
741
Resources
0
Go to "Admin Settings" -> "List Nodes" -> "[your node name]" -> "Auto-Deploy" -> "Generate Deployment Script". Then go to your SSH console and copy that in the terminal.
tried earlier, but I always get this error message:


dpkg: error processing package mysql-server-5.5 (--configure):
subprocess installed post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration of mysql-server:
mysql-server depends on mysql-server-5.5; however:
Package mysql-server-5.5 is not configured yet.
dpkg: error processing package mysql-server (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mysql-server-5.5
mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
An error occured while installing, halting...
 

Jayson

Supreme
Feedback score
17
Posts
1,258
Reactions
741
Resources
0
Looks like something is messed up with your MySQL installation. The mysql.user table should definitely exist. Try running this:
Code:
sudo mysql_install_db
If that doesn't work, maybe the permissions on your MySQL data directory are messed up. You could also try re-installing MySQL completely.
Installing MySQL system tables...
161214 23:23:01 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
161214 23:23:01 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
161214 23:23:01 [Note] /usr/sbin/mysqld (mysqld 5.5.53-0ubuntu0.14.04.1) starting as process 8989 ...
OK
Filling help tables...
161214 23:23:02 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
161214 23:23:02 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
161214 23:23:02 [Note] /usr/sbin/mysqld (mysqld 5.5.53-0ubuntu0.14.04.1) starting as process 8996 ...
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h apollomc password 'new-password'
Alternatively you can run:
/usr/bin/mysql_secure_installation
which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.
See the manual for more instructions.
You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &
You can test the MySQL daemon with mysql-test-run.pl
cd /usr/mysql-test ; perl mysql-test-run.pl


I ran MySQL_secure_installation again, no errors, but i'm back to "An error occured while trying to connect to the remote node. Please check that Scales is running and try again." I'll reinstall it all later, midnight right now. Thx for the help.
 
Status
This thread has been locked.
Top