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?
Related
When trying to start Yagna I receive this error, what can I do? I can probably get some DEBUG logs if needed?
[2021-05-06T08:45:08Z INFO yagna] Starting yagna service! Version: 0.6.4 (4fc72117 2021-04-15 build #135).
Log is written to /home/user/.local/share/yagna/yagna_rCURRENT.log
[2021-05-06T08:45:08Z INFO yagna] Data directory: /home/user/.local/share/yagna
[2021-05-06T08:45:08Z INFO ya_sb_router::unix] Router listening on: "/tmp/yagna.sock"
[2021-05-06T08:45:08Z INFO ya_persistence::executor] using database at: /home/user/.local/share/yagna/yagna.db
[2021-05-06T08:45:08Z INFO ya_persistence::executor] using database at: /home/user/.local/share/yagna/market.db
[2021-05-06T08:45:08Z INFO ya_persistence::executor] using database at: /home/user/.local/share/yagna/activity.db
[2021-05-06T08:45:08Z INFO ya_persistence::executor] using database at: /home/user/.local/share/yagna/payment.db
[2021-05-06T08:45:08Z INFO ya_identity::service::identity] using default identity: 0xf5ecffecf053508fe97255e046a04ce21c8ee525
[2021-05-06T08:45:08Z INFO yagna] Identity GSB service successfully activated
[2021-05-06T08:45:08Z INFO ya_metrics::pusher] Metrics pusher started
[2021-05-06T08:45:08Z INFO yagna] Metrics GSB service successfully activated
[2021-05-06T08:45:08Z INFO ya_service_bus::remote_router] trying to connect to: /tmp/yagna.sock
[2021-05-06T08:45:08Z INFO ya_service_bus::connection] started connection to gsb
[2021-05-06T08:45:08Z INFO ya_metrics::pusher] Starting metrics pusher
[2021-05-06T08:45:10Z INFO yagna] Version GSB service successfully activated
[2021-05-06T08:45:10Z INFO ya_net::service] using default identity as network id: 0xf5ecffecf053508fe97255e046a04ce21c8ee525
[2021-05-06T08:45:10Z WARN ya_net::handler] Failed to bind handlers: DNS Error: Not Implemented; retrying in 2 s
[2021-05-06T08:45:12Z WARN ya_net::handler] Failed to bind handlers: DNS Error: Not Implemented; retrying in 4 s
[2021-05-06T08:45:16Z WARN ya_net::handler] Failed to bind handlers: DNS Error: Not Implemented; retrying in 8 s
EDIT: nslookup
Server: 10.139.1.1
Address: 10.139.1.1#53
** server can't find _net._tcp.dev.golem.network: NOTIMP
I'm not sure what is the reason here, but it seems like DNS is not able to resolve _net._tcp.dev.golem.network SRV record yielding 'Not Implemented'. It is very odd, since Yagna is using Google's DNS servers as a default.
When you face this again pls try to check output of following command
nslookup -q=SRV _net._tcp.dev.golem.network 8.8.8.8
The user has trouble reaching Google's DNS with nslookup, so it appears to be something on his end. He is also using a proxy for his connection, so it must happen somewhere in there. Closing thread.
I have configured openldap manually on opensuse 42.3 and it's working fine until i didn't configure LDAP and Kerberos Client. after i configure use a directory as identity provider and checked(BEFORE REBOOT) getent passwd. i was able to see the users and able to login.After reboot the system the below error is coming:
[FAILED] Failed to start Avahi mDNS/DNS-SD stack
see systemctl status avahi-daemon.service for detials
[FAILED] Failed to start wicked AutoIPv4 supplicant service
see systemctl status wickedd-auto4.service for details
[FAILED] Failed to start wicked DHCPv6 supplicant service
see systemctl status wickedd DHCPv6 supplicant service for details
[FAILED] Failed to start wicked DHCPV4 supplicant service
see systemctl status wickedd-dhcp4.service for details
I found the answer for my question?
we have to enter bind_policy soft in vim /etc/ldap.conf file. so you don't get an error further
I am installing ICp 2.1.0.1 and I received an error at the TASK
[master: Waiting for MariaDB service to start] msg: The MariaDB
component failed to start.
After this msg the installation completed with failed status.
We are installing ICp with 3 Masters, 3 Proxies and 2 Workers. We have 1 IP for VIP master and 1 for VIP proxy.
I tried to install multiple times and all installations got the same error.
For prior issues with that error, the correct db admin password was not used. So check the db user and password to resolve issue.
Would you validate whether each master host was able to access port 3306 on the other hosts?
If you run with .. install -vv | tee -a install-log.txt, do you get additional details as well?
The error was solved by following the steps below.
Check whether kubelet is running:
Log in to your master node.
Run the following command to check kubelet status:
systemctl status kubelet
If kubelet is not running, run the following command to get the logs:
journalctl -u kubelet &> kubelet.log
We found the error in the kubelet.log log:
Error: failed to run Kubelet: Running with swap on is not supported, please disable swap! or set --fail-swap-on flag to false.
We found this troubleshoot in this link, and the solution at the ICP issue 4651.
https://www.ibm.com/support/knowledgecenter/en/SSBS6K_2.1.0/troubleshoot/etcd_fails.html
https://github.ibm.com/IBMPrivateCloud/roadmap/issues/4651
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
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.