When I start Tor bundle on Ubuntu 18.04 I get an error:
Jul 11 11:25:05.000 [debug] command_process_destroy_cell(): Received for circID 3910604357.
Jul 11 11:25:05.000 [info] circuit_mark_for_close_(): Circuit 0 (id: 37) marked for close at ../src/core/or/command.c:654 (orig reason: 517, new reason: 0)
Jul 11 11:25:05.000 [debug] connection_or_process_cells_from_inbuf(): 13: starting, inbuf_datalen 0 (0 pending in tls object).
Jul 11 11:25:05.000 [debug] circuit_increment_failure_count(): n_circuit_failures now 6.
Jul 11 11:25:05.000 [info] circuit_free_(): Circuit 0 (id: 37) has been freed.
Jul 11 11:25:05.000 [debug] circuit_remove_handled_ports(): Port 443 is not handled.
Jul 11 11:25:05.000 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal), need another exit circ.
Jul 11 11:25:06.000 [debug] circuit_remove_handled_ports(): Port 443 is not handled.
Jul 11 11:25:06.000 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal), need another exit circ.
Jul 11 11:25:07.000 [debug] circuit_remove_handled_ports(): Port 443 is not handled.
Jul 11 11:25:07.000 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal), need another exit circ.
Jul 11 11:25:08.000 [debug] circuit_remove_handled_ports(): Port 443 is not handled.
Jul 11 11:25:08.000 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal), need another exit circ.
I've installed Tor bundle from official Tor repo. What have I to do to prevent this error?
Related
I am unable to restart my apache server to successfully install the SSL certificates.
I get the following error
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
I have tried several articles and the root cause seems to be the following
Mar 29 13:05:09 localhost.localdomain httpd\[1234546\]: (98)Address already in use: AH00072: make_sock: could not bind to address \[::\]:80
Mar 29 13:05:09 localhost.localdomain httpd\[1234546\]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
I am able to diagnose the issue and get the following output and is also attached. I am unable to proceed further. Can you please help ?
Server - AlmaLinux 8
Host - IONOS
Server version: Apache/2.4.37 (AlmaLinux)
-- Unit session-62994.scope has finished starting up.
-
-- Unit session-62994.scope has finished starting up.
-
-- The unit session-62994.scope has successfully entered the 'dead' state.
Mar 31 06:07:10 localhost.localdomain dhclient\[1326\]: XMT: Solicit on ens192, interval 110600ms.
Mar 31 06:07:10 localhost.localdomain dhclient\[1326\]: RCV: Advertise message on ens192 from fe80::250:56ff:fe8c:84c6.
Mar 31 06:07:10 localhost.localdomain dhclient\[1326\]: RCV: Advertise message on ens192 from fe80::250:56ff:fe9a:f13a.
Mar 31 06:07:30 localhost.localdomain sshd\[1297516\]: Invalid user sui from 167.99.68.65 port 48488
Mar 31 06:07:30 localhost.localdomain sshd\[1297516\]: pam_unix(sshd:auth): check pass; user unknown
Mar 31 06:07:30 localhost.localdomain sshd\[1297516\]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.68.65
Mar 31 06:07:32 localhost.localdomain sshd\[1297516\]: Failed password for invalid user sui from 167.99.68.65 port 48488 ssh2
Mar 31 06:07:34 localhost.localdomain sshd\[1297516\]: Received disconnect from 167.99.68.65 port 48488:11: Bye Bye \[preauth\]
Mar 31 06:07:34 localhost.localdomain sshd\[1297516\]: Disconnected from invalid user sui 167.99.68.65 port 48488 \[preauth\]
Mar 31 06:07:44 localhost.localdomain unix_chkpwd\[1297520\]: password check failed for user (root)
Mar 31 06:07:44 localhost.localdomain sshd\[1297518\]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.173.27 user=root
Mar 31 06:07:46 localhost.localdomain sshd\[1297518\]: Failed password for root from 61.177.173.27 port 58626 ssh2
Mar 31 06:07:46 localhost.localdomain unix_chkpwd\[1297521\]: password check failed for user (root)
\[root#localhost \~\]# ss --listening --tcp --numeric --processes
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 128 0.0.0.0:80 0.0.0.0:\* users:(("nginx",pid=1087,fd=10),("nginx",pid=1086,fd=10),("nginx",pid=1084,fd=10))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:\* users:(("sshd",pid=1335,fd=5))
LISTEN 0 128 0.0.0.0:443 0.0.0.0:\* users:(("nginx",pid=1087,fd=11),("nginx",pid=1086,fd=11),("nginx",pid=1084,fd=11))
LISTEN 0 128 \[::\]:22 \[::\]:\* users:(("sshd",pid=1335,fd=7))
LISTEN 0 80 \*:3306 *:* users:(("mysqld",pid=1098,fd=19))
Tried -
apachectl configtest - Result: syntax ok
setenforce 0
Unable to start Apache2 server after I modifed dir.conf file, even after changing it back to normal
I modified /etc/apache2/mods-enabled/dir.conf and changed the order and wrote index.php in
the first place before index.html, so the file contents have been modified from
"DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm" to now
"DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm". But still
changing that back to original order, also does not start apache2 server, it gives the same
error. I tried restarting and stop and start, but none seem to work.
** Here are the details of systemctl status apache2.service **
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Tue 2020-11-24 12:28:31 IST; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 20300 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 25755 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)
Nov 24 12:28:31 localhost apache2[25755]: *
Nov 24 12:28:31 localhost apache2[25755]: * The apache2 configtest failed.
Nov 24 12:28:31 localhost apache2[25755]: Output of config test was:
Nov 24 12:28:31 localhost apache2[25755]: AH00534: apache2: Configuration error: More than one MPM loaded.
Nov 24 12:28:31 localhost apache2[25755]: Action 'configtest' failed.
Nov 24 12:28:31 localhost apache2[25755]: The Apache error log may have more information.
Nov 24 12:28:31 localhost systemd[1]: apache2.service: Control process exited, code=exited status=1
Nov 24 12:28:31 localhost systemd[1]: Failed to start LSB: Apache2 web server.
Nov 24 12:28:31 localhost systemd[1]: apache2.service: Unit entered failed state.
Nov 24 12:28:31 localhost systemd[1]: apache2.service: Failed with result 'exit-code'.
**Here is the details of journalctl -xe**
Nov 24 12:44:42 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:42 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
Nov 24 12:44:43 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:43 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
Nov 24 12:44:44 localhost systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Nov 24 12:44:44 localhost systemd[1]: mysql.service: Unit entered failed state.
Nov 24 12:44:44 localhost systemd[1]: mysql.service: Failed with result 'exit-code'.
Nov 24 12:44:44 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:44 localhost systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Nov 24 12:44:44 localhost systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Nov 24 12:44:44 localhost systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.545855Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.545908Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.705792Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --expl
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.707018Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.32-0ubuntu0.16.04.1) starting as process 538
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.709650Z 0 [ERROR] Could not open file '/var/log/mysql/error.log' for error logging: No suc
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.709678Z 0 [ERROR] Aborting
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.709703Z 0 [Note] Binlog end
Nov 24 12:44:44 localhost mysqld[5387]: 2020-11-24T07:14:44.709770Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
Nov 24 12:44:44 localhost systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Nov 24 12:44:44 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
Nov 24 12:44:44 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:45 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
Nov 24 12:44:45 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:75]
Nov 24 12:44:45 localhost kernel: [drm:drm_mode_addfb2 [drm]] [FB:77]
I am trying to start a django project using an AWS EC2 linux server using putty on windows, however Apache2 is showing an error related to the fact that the address is already used as shown in the next code:
apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2020-07-25 19:51:59 UTC; 2min 7s ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 15022 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Jul 25 19:51:59 ip-172-31-4-25 apachectl[15022]: AH00558: apache2: Could not reliably determine
the server's fully qualified domain name, using 127.0.0.1. Set the 'Serv
Jul 25 19:51:59 ip-172-31-4-25 apachectl[15022]: (98)Address already in use: AH00072: make_sock:
could not bind to address [::]:80
Jul 25 19:51:59 ip-172-31-4-25 apachectl[15022]: (98)Address already in use: AH00072: make_sock:
could not bind to address 0.0.0.0:80
Jul 25 19:51:59 ip-172-31-4-25 apachectl[15022]: no listening sockets available, shutting down
Jul 25 19:51:59 ip-172-31-4-25 apachectl[15022]: AH00015: Unable to open logs
Jul 25 19:51:59 ip-172-31-4-25 apachectl[15022]: Action 'start' failed.
Jul 25 19:51:59 ip-172-31-4-25 apachectl[15022]: The Apache error log may have more information.
Jul 25 19:51:59 ip-172-31-4-25 systemd[1]: apache2.service: Control process exited, code=exited,
status=1/FAILURE
Jul 25 19:51:59 ip-172-31-4-25 systemd[1]: apache2.service: Failed with result 'exit-code'.
Jul 25 19:51:59 ip-172-31-4-25 systemd[1]: Failed to start The Apache HTTP Server.
I already tried to verify the status of the network using the next code, but the failure still the same.
systemctl status apache2.service
I also tried to verify the service listening ports using the next code, and the output was:
bitnami#ip-172-31-4-25:~$ sudo netstat -ntlp | grep 80
tcp6 0 0 :::80 :::* LISTEN 15122/httpd
I would appreciate any recommendation on it.
Check Skype, if its running then close first and then start Apache service.
Skype also use port 80.
I have an Ubuntu VM 20.04LTS where I installed tsunami-security-scanner and also run the docker example with a vulnerable image.
The example works as expected founding a vulnerability: JUPYTER_NOTEBOOK_EXPOSED_UI
When I tried with a live target I have, I got the following JSON otuput:
{
"scanStatus": "PARTIALLY_SUCCEEDED",
"scanStartTimestamp": "2020-07-09T03:35:32.611Z",
"scanDuration": "45.315s",
"fullDetectionReports": {
},
"statusMessage": "Failed plugins:\n/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/NcrackWeakCredentialDetectorPlugin/0.1\n/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/WordPressInstallPageDetector/0.1"
}
NcrackWeakCredentialDetectorPlugin and WordPressInstallPageDetector have failed but don't know why.
This is the console output:
(...)
Jul 10, 2020 1:00:33 AM com.google.tsunami.workflow.DefaultScanningWorkflow fingerprintNetworkServices
INFO: Port scanning phase done, moving to service fingerprinting phase with '0' fingerprinter(s) selected.
Jul 10, 2020 1:00:34 AM com.google.tsunami.workflow.DefaultScanningWorkflow detectVulnerabilities
INFO: Service fingerprinting phase done, moving to vuln detection phase.
Jul 10, 2020 1:00:34 AM com.google.tsunami.plugins.detectors.credentials.ncrack.NcrackWeakCredentialDetector detect
INFO: Starting weak credential detection using ncrack.
Jul 10, 2020 1:00:34 AM com.google.tsunami.plugins.detectors.exposedui.hadoop.yarn.YarnExposedManagerApiDetector detect
INFO: Starting unauthenticated Apache Yarn ResourceManager API detection
Jul 10, 2020 1:00:34 AM com.google.tsunami.plugins.detectors.exposedui.jenkins.JenkinsExposedUiDetector detect
INFO: Starting exposed ui detection for Jenkins
Jul 10, 2020 1:00:34 AM com.google.tsunami.plugins.detectors.exposedui.jupyter.JupyterExposedUiDetector detect
INFO: Starting exposed ui detection for Jupyter Notebook
Jul 10, 2020 1:00:34 AM com.google.tsunami.plugins.detectors.exposedui.wordpress.WordPressInstallPageDetector detect
INFO: Starting unfinished install page detection for WordPress.
Jul 10, 2020 1:00:34 AM com.google.tsunami.common.net.http.HttpClient send
INFO: Sending HTTP 'GET' request to 'http://xxx.xxx.xxx.xxx/terminals/1'.
Jul 10, 2020 1:00:34 AM com.google.tsunami.common.net.http.HttpClient send
INFO: Sending HTTP 'GET' request to 'http://xxx.xxx.xxx.xxx/cluster/cluster'.
Jul 10, 2020 1:00:34 AM com.google.tsunami.common.net.http.HttpClient send
INFO: Sending HTTP 'GET' request to 'http://xxx.xxx.xxx.xxx/view/all/newJob'.
Jul 10, 2020 1:00:34 AM com.google.tsunami.common.net.http.HttpClient send
INFO: Sending HTTP 'GET' request to 'http://xxx.xxx.xxx.xxx/wp-login.php'.
Jul 10, 2020 1:00:34 AM com.google.tsunami.common.net.http.HttpClient send
INFO: Sending HTTP 'GET' request to 'http://xxx.xxx.xxx.xxx/wp-admin/install.php?step=1'.
Jul 10, 2020 1:00:35 AM com.google.tsunami.common.net.http.HttpClient parseResponse
INFO: Received HTTP response with code '404' for request to 'http://xxx.xxx.xxx.xxx/view/all/newJob'.
Jul 10, 2020 1:00:35 AM com.google.tsunami.common.net.http.HttpClient parseResponse
INFO: Received HTTP response with code '404' for request to 'http://xxx.xxx.xxx.xxx/cluster/cluster'.
Jul 10, 2020 1:00:35 AM com.google.tsunami.common.net.http.HttpClient parseResponse
INFO: Received HTTP response with code '404' for request to 'http://xxx.xxx.xxx.xxx/terminals/1'.
Jul 10, 2020 1:00:35 AM com.google.tsunami.common.net.http.HttpClient parseResponse
INFO: Received HTTP response with code '200' for request to 'http://xxx.xxx.xxx.xxx/wp-login.php'.
Jul 10, 2020 1:00:35 AM com.google.tsunami.plugin.PluginExecutorImpl buildFailedResult
WARNING: Plugin '/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/NcrackWeakCredentialDetectorPlugin/0.1' failed.
Jul 10, 2020 1:00:35 AM com.google.tsunami.plugins.detectors.exposedui.hadoop.yarn.YarnExposedManagerApiDetector detect
INFO: YarnExposedManagerApiDetector finished, detected '0' vulns.
Jul 10, 2020 1:00:35 AM com.google.tsunami.common.net.http.HttpClient parseResponse
INFO: Received HTTP response with code '200' for request to 'http://xxx.xxx.xxx.xxx/wp-admin/install.php?step=1'.
Jul 10, 2020 1:00:35 AM com.google.tsunami.plugin.PluginExecutorImpl buildFailedResult
WARNING: Plugin '/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/WordPressInstallPageDetector/0.1' failed.
Jul 10, 2020 1:00:35 AM com.google.tsunami.workflow.DefaultScanningWorkflow generateScanResults
INFO: Tsunami scanning workflow done. Generating scan results.
Jul 10, 2020 1:00:35 AM com.google.tsunami.workflow.DefaultScanningWorkflow lambda$runAsync$0
INFO: Tsunami scanning workflow traces:
Port scanning phase (28.90 s) with 1 plugin(s):
/Tsunami Team (tsunami-dev#google.com)/PORT_SCAN/NmapPortScanner/0.1
Service fingerprinting phase (759.9 ms) with 0 plugin(s):
Vuln detection phase (694.7 ms) with 5 plugin(s):
/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/NcrackWeakCredentialDetectorPlugin/0.1 was selected for the following services: http (TCP, port 80), ssh (TCP, port 8080)
/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/YarnExposedManagerApiDetector/0.1 was selected for the following services: http (TCP, port 80), ssh (TCP, port 8080)
/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/JenkinsExposedUiDetector/0.1 was selected for the following services: http (TCP, port 80), ssh (TCP, port 8080)
/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/JupyterExposedUiDetector/0.1 was selected for the following services: http (TCP, port 80), ssh (TCP, port 8080)
/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/WordPressInstallPageDetector/0.1 was selected for the following services: http (TCP, port 80), ssh (TCP, port 8080)
# of detected vulnerability: 0.
Jul 10, 2020 1:00:35 AM com.google.tsunami.main.cli.TsunamiCli run
INFO: Tsunami scan finished, saving results.
Jul 10, 2020 1:00:35 AM com.google.tsunami.common.io.archiving.RawFileArchiver archive
INFO: Archiving data to file system with filename '/tmp/tsunami-output.json'.
Jul 10, 2020 1:00:35 AM com.google.tsunami.main.cli.TsunamiCli run
INFO: TsunamiCli finished...
Jul 10, 2020 1:00:35 AM com.google.tsunami.main.cli.TsunamiCli main
INFO: Full Tsunami scan took 38.52 s.
kali#kali:~/tsunami/plugins$ ls -l
total 340
-rw-r--r-- 1 kali kali 7145 Jul 9 15:13 exposed_hadoop_yarn_api-0.0.1-SNAPSHOT.jar
-rw-r--r-- 1 kali kali 6179 Jul 9 15:13 exposed_jenkins_ui-0.0.1-SNAPSHOT.jar
-rw-r--r-- 1 kali kali 5888 Jul 9 15:13 exposed_jupyter_notebook-0.0.1-SNAPSHOT.jar
-rw-r--r-- 1 kali kali 41535 Jul 9 15:13 ncrack_weak_credential_detector-0.0.1-SNAPSHOT.jar
-rw-r--r-- 1 kali kali 267309 Jul 9 15:13 nmap_port_scanner-0.0.1-SNAPSHOT.jar
-rw-r--r-- 1 kali kali 6248 Jul 9 15:13 wordpress_exposed_installation_page-0.0.1-SNAPSHOT.jar
kali#kali:~/tsunami$ nmap -v
Starting Nmap 7.80 ( https://nmap.org ) at 2020-07-10 01:02 EDT
Read data files from: /usr/bin/../share/nmap
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 0.07 seconds
kali#kali:~/tsunami$ ncrack -v
Starting Ncrack 0.7 ( http://ncrack.org ) at 2020-07-10 01:03 EDT
No services specified!
QUITTING!
I made a focus on these two lines:
WARNING: Plugin '/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/NcrackWeakCredentialDetectorPlugin/0.1' failed.
WARNING: Plugin '/Tsunami Team (tsunami-dev#google.com)/VULN_DETECTION/WordPressInstallPageDetector/0.1' failed.
The same plugins worked before against the docker example.
I also set up a Kali 2020.2 VM with tsunami-security-scanner, just to check what happens to have the docker image in a VM and running the Tsunami in another VM.
Again worked as expected.
I can't figure out what is failing.
Thanks in advance!
My node-red installation does not display the nodes needed for accessing beaglebone IOs (node-red-node-beaglebone).
In my opinion error is actually caused because node-red-node-beaglebone loads octalbonescript which needs serialport, and something requests serialPort instead of serialport there.
I already tried the preinstalled, stable and lts nodejs version. Additionally npm#2 and npm#3 for installing the nodes. The .node-red folder was also already deleted by me and the node-red-node-beaglebone packaged got installed in the .node-red/node_modules folder started from scrach.
root#beaglebone:/etc# cat debian_version
8.7
root#beaglebone:~# npm -v
2.15.11
root#beaglebone:~# uname -a
Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Linux
root#beaglebone:~# export AUTO_LOAD_CAPE=0 #optional
root#beaglebone:~# node-red-pi
1487183133432 Board Looking for connected device
15 Feb 19:25:34 - [info]
Welcome to Node-RED
===================
15 Feb 19:25:34 - [info] Node-RED version: v0.16.2
15 Feb 19:25:34 - [info] Node.js version: v6.9.5
15 Feb 19:25:34 - [info] Linux 4.4.30-ti-r64 arm LE
15 Feb 19:25:44 - [info] Loading palette nodes
15 Feb 19:25:57 - [warn] ------------------------------------------------------
15 Feb 19:25:57 - [warn] [bbb] ReferenceError: serialPort is not defined +seems to be the problem
15 Feb 19:25:57 - [warn] ------------------------------------------------------
15 Feb 19:25:57 - [info] Settings file : /root/.node-red/settings.js
15 Feb 19:25:57 - [info] User directory : /root/.node-red
15 Feb 19:25:57 - [info] Flows file : /root/.node-red/flows_beaglebone.json
15 Feb 19:25:57 - [info] Creating new flow file
15 Feb 19:25:57 - [debug] loaded flow revision: 513fd923d68021b8ee98fcb250470340
15 Feb 19:25:57 - [debug] red/runtime/nodes/credentials.load : no user key present
15 Feb 19:25:57 - [debug] red/runtime/nodes/credentials.load : using default key
15 Feb 19:25:57 - [info] Starting flows
15 Feb 19:25:57 - [info] Started flows
15 Feb 19:25:57 - [info] Server now running at http://127.0.0.1:1880/