I install ROS on my server, but when I called ros start and it will running at my server, here is the log:
login as: root
root#*.*.*.*'s password:
Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-109-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
Welcome to Alibaba Cloud Elastic Compute Service !
root#iZwz940pq66re8qvh8adzuZ:~# ros start
info: Loaded feature token capabilities=[Sync], expires=Wed Apr 19 2017 22:15:29 GMT+0800 (CST)
info: Realm Object Server version 2.5.1 is starting
info: [sync] Realm sync server started ([realm-core-4.0.4], [realm- sync-2.1.10])
info: [sync] Directory holding persistent state: /root/data/sync/user_data
info: [sync] Operating mode: master_with_no_slave
info: [sync] Log level: info
info: [sync] Download log compaction is enabled
info: [sync] Max download size: 131072 bytes
info: [sync] Listening on 127.0.0.1:35571 (sync protocol version 22)
info: Realm Object Server has started and is listening on http://0.0.0.0:9080
But when I entered the address in the browser, It told me that I could not connect.And I use Realm Studio to connect it also tell me that could not reach the server, did i forget something steps? Maybe my server's security policy forbide the port?
Per to the log description, Realm Object Server has started and is listening on http://0.0.0.0:9080.
Please ensure you've allowed TCP port 9080 in your ECS security group.
For detail steps, please refer the document
Add a security group rule
Related
Running on ubuntu server:
sudo openfortivpn --trusted-cert 6f0ac15ce35ca1y3253a6307874ffd490029f3c2eba7a1ec289eda308b95cbf13 portal2.assd.bb.com:10443 -u user <<< 'pass'
I get this ouput
INFO: Connected to gateway.
INFO: Authenticated.
INFO: Remote gateway has allocated a VPN.
ERROR: read: Input/output error
INFO: Cancelling threads...
ERROR: pppd: Is not setuid-root and the invoking user is not root.
INFO: Terminated pppd.
INFO: Closed connection to gateway.
INFO: Logged out.
openfortivpn --version
1.6.0
How can I solve it? ppp is alredy installed. Where can I read: read: Input/output error?
Artifactory Pro 7.33.12 Running on SLES 12-SP5
I did not configure the Replicator in system.yaml or somewhere else.
After restart from Artifactory always appears in console.log (No problem. Message exists since installing Artifactory last year):
2022-04-26T10:47:12... [.c.r.ReplicatorServiceImpl:119] [art-init- initializing Replicator Service
2022-04-26T10:47:12..[c.r.ReplicatorServiceImpl:338] [art-init] - Local Replicator is setting up in non-bundled mode
But suddenly appearing messages by restarting Artifactory:
Info: Replicator is starting
Replicator configured successfully
Replicator Version:release/20220124145455-preRelease-jfpdn-7-30-x-rc.1
Supporting mime-type: application/java-archive
Supporting mime-type: application/x-nupkg
Supporting mime-type: application/x-tar
Supporting mime-type: application/zip
registering profiling endpoints:localhost:8041
Initializing internal http client
replicator service id:jfxfer#01fdsky4nnnd301nzwzzey1cb4
Using Artifactory Blob Store in address: http://localhost:8046/artifactory
Replicator listening on localhost:8048
And every minute:
Initializing Replicator registration
url: http://localhost:8046/artifactory/api/replicator/register
token: eyJ2ZXIiOi****
Replicator registration request was forbidden (make sure Enterprise Plus license installed)
$JFROG_HOME/artifactory/app/replicator/bin/replicator.sh status
Replicator is not running
ps -eaf|grep replicator
artifac+ 17911 1 0 15:21 ? 00:00:00 $JFROG_HOME/artifactory/app/replicator/bin/jf-replicator --replicatorHome=$JFROG_HOME/artifactory/app/replicator
To kill the process is no good idea.
Every 5 seconds appears:
Readiness test failed with the following error: "required node services are missing or unhealthy"
The insert in system.yaml
## REPLICATOR TEMPLATE
replicator:
## Set to true if using an Enterprise Plus license
enabled: false
#port: 8048
has no effect.
What happened and how to stop the Replicator?
Does anyone have an answer?
I host a web site with Nginx in Debian in google cloud.
when I install code server and i visit: my_ip:8443, chrome replied with: ERR_CONNECTION_TIMED_OUT.
when I execute the command code-server:
INFO code-server v1.1156-vsc1.33.1
INFO Additional documentation: http://github.com/cdr/code-server
INFO Initializing {"data-dir":"/home/naji/.local/share/code-server","extensions-dir":"/home/naji/.local/share/code-server/extensions","working-dir":"/","log-dir":"/home/naji/.cache/code-server/logs/20190723145420188"}
INFO Starting webserver... {"host":"0.0.0.0","port":8443}
WARN No certificate specified. This could be insecure.
WARN Documentation on securing your setup: https://github.com/cdr/code-server/blob/master/doc/security/ssl.md
INFO
INFO Password: ******************
INFO
INFO Started (click the link below to open):
INFO https://localhost:8443/
INFO
INFO Starting shared process [1/5]...
WARN stderr {"data":"(node:17025) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.\n"}
INFO Connected to shared process
what is the solution ?
I am following the Getting started guide for the Realm Mobile Platform. I started the Realm Object server and run the Mac OSX demo task app. I cannot however connect to the object server using the Mac OSX Realm Browser app.
I open the Realm Browser and select Connect to Object Server. I enter realm://127.0.0.1:9080 as the server url and then paste in the long token string ending in == that I get from terminal when I started the Object server with the command start-object-server.command. I now click connect and get the following error:
Failed to connect to Object Server.
Check the url and that the server is accessible.
In terminal I see a log saying that I need to login to http://127.0.0.1:27080/ and create an admin user. I navigate to that url and can see my user which is an admin.
Here are the logs:
info: Logging to console at level 'info'.
info: Realm Object Server sync server listening on 127.0.0.1:27800.
info: Realm Object Server web server listening on 127.0.0.1:27080.
info: http proxy listening on 0.0.0.0:9080.
info: sync-server: Realm sync server started ([realm-core-2.0.0], [realm-sync-1.0.0-BETA-1.0])
info: sync-server: Directory holding persistent state: /Users/grant/Apps/realm-mobile-platform/realm-object-server/object-server/root_dir/user_data
info: sync-server: Listening on 127.0.0.1:27800 (sync protocol version 14)
info: The Realm Object Server requires an initial admin user to start. To continue, please open your web browser to access the dashboard at: http://127.0.0.1:27080 and register your user.
info: sync-server: Connection[1]: Connection from 127.0.0.1:53352
info: sync-server: Connection[1]: Received: CLIENT(protocol_version=14, client_info_size=2, client_info = {})
info: sync-server: Connection[1]: Session[1]: Initiated
info: sync-server: Connection[1]: Session[1]: Received: BIND(server_path='/__admin', signed_user_token=eyJpZGVudGl0eSI6ImF1..., need_file_ident_pair=0)
info: sync-server: Connection[1]: Session[1]: Received: IDENT(server_file_ident=80096, client_file_ident=1, client_file_ident_secret=523599, scan_server_version=13, scan_client_version=24, latest_server_version=13, latest_server_session_ident=7426485)
When I run telnet localhost 9080 I get the following output:
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Any idea why I cannot connect to the object server using the Mac OSX Realm Browser app?
I re-downloaded the latest Realm files and everything works as expected now.
After adding plone.app.async, I cannot start my production instances normally using 'bin/instance start'. However, the instances run fine using 'foreground' and I can start the production instances on my development machine just fine. (The machines have almost identical configurations but the production machine has almost 100GB of data in blob storage.)
Additionally, I can start the instances normally if I remove support for plane.app.async, specifically the zcml-additions section, from my buildout. And I can start the worker instance for plone.app.async just fine. It uses almost all the same sections as the regular instances except for 'zcml-additional' being for worker instead of instance.
This happens with both single and multi db for plone.app.async.
The instance log shows that it gets trapped in some sort of cycle during startup. Here is the log of what happens:
....
2012-02-09T18:31:27 INFO ZServer HTTP server started at Thu Feb 9 18:31:27 2012
Hostname: 0.0.0.0
Port: 8081
2012-02-09T18:31:32 INFO ZServer WebDAV server started at Thu Feb 9 18:31:32 2012
Hostname: 0.0.0.0
Port: 1980
2012-02-09T18:31:32 INFO Zope Set effective user to "plone"
2012-02-09T18:31:34 INFO ZEO.ClientStorage zeostorage ClientStorage (pid=16331) created RW/normal for storage: '1'
2012-02-09T18:31:34 INFO ZEO.cache created temporary cache file '<fdopen>'
2012-02-09T18:31:34 INFO ZEO.ClientStorage zeostorage Testing connection <ManagedClientConnection ('127.0.0.1', 8100)>
2012-02-09T18:31:34 INFO ZEO.zrpc.Connection(C) (127.0.0.1:8100) received handshake 'Z3101'
2012-02-09T18:31:34 INFO ZEO.ClientStorage zeostorage Server authentication protocol None
2012-02-09T18:31:34 INFO ZEO.ClientStorage zeostorage Connected to storage: ('localhost', 8100)
2012-02-09T18:31:34 INFO ZEO.ClientStorage zeostorage No verification necessary -- empty cache
2012-02-09T18:31:45 INFO ZServer HTTP server started at Thu Feb 9 18:31:45 2012
Hostname: 0.0.0.0
Port: 8081
2012-02-09T18:31:50 INFO ZServer WebDAV server started at Thu Feb 9 18:31:50 2012
Hostname: 0.0.0.0
Port: 1980
....
This repeats forever.
With a logging level of debug, I receive the following output: http://pastebin.com/nnyekuRA
Around line 58 is what I think is the culprit:
2012-02-09T17:18:22 DEBUG ZEO.ClientStorage pickled inval None '\x03\x94X\x8a\xa8\xe9\xf6\xee'
------
2012-02-09T17:18:22 BLATHER ZEO.zrpc (15892) CM.connect_done(preferred=1)
------
2012-02-09T17:18:22 BLATHER ZEO.zrpc (15892) CT: exiting thread: Connect([(2, ('127.0.0.1', 8100))])
But I have no idea why this is happening or even if this is correct.
Here is the buildout for deployment:
http://pastebin.com/u8D7swJs
The permissions were set incorrectly on the Plone 'parts' directory. This prevented 'uuid.txt' from being written in 'parts/instance/' . There were no error messages to indicate this problem.