I installed JFrog standalone version on Ubuntu. I dont know my JFrog username and password. I also checked /usr/lib/apache-tomcat-8.5.16/conf/server.xml file but it is does not have any username and password. I also clicked on set me up, but the commandline interface to push an artifact is also prompting for username and password.
ravi#ravi-Inspiron-5537:~$ systemctl status artifactory.service
● artifactory.service - Setup Systemd script for Artifactory in Tomcat Servlet E
Loaded: loaded (/lib/systemd/system/artifactory.service; enabled; vendor pres
Active: active (running) since Fri 2017-08-11 10:11:41 EDT; 37min ago
Process: 16482 ExecStart=/opt/jfrog/artifactory/bin/artifactoryManage.sh start
Main PID: 16532 (java)
CGroup: /system.slice/artifactory.service
‣ 16532 /usr/bin/java -Djava.util.logging.config.file=/opt/jfrog/arti
Aug 11 10:11:17 ravi-Inspiron-5537 su[16508]: Successful su for artifactory by r
Aug 11 10:11:17 ravi-Inspiron-5537 su[16508]: + ??? root:artifactory
Aug 11 10:11:17 ravi-Inspiron-5537 su[16508]: pam_unix(su:session): session open
Aug 11 10:11:18 ravi-Inspiron-5537 artifactoryManage.sh[16482]: Max number of op
Aug 11 10:11:18 ravi-Inspiron-5537 artifactoryManage.sh[16482]: Using ARTIFACTOR
Aug 11 10:11:18 ravi-Inspiron-5537 artifactoryManage.sh[16482]: Using ARTIFACTOR
Aug 11 10:11:18 ravi-Inspiron-5537 artifactoryManage.sh[16482]: Creating directo
Aug 11 10:11:18 ravi-Inspiron-5537 artifactoryManage.sh[16482]: Tomcat started.
Aug 11 10:11:41 ravi-Inspiron-5537 artifactoryManage.sh[16482]: Artifactory Tomc
Aug 11 10:11:41 ravi-Inspiron-5537 systemd[1]: Started Setup Systemd script for
lines 1-18/18 (END)
The default username and password of Artifactory are:
User: admin
Pass: password
Related
I have a problem with connecting to VPN. When I start up the raspberry device and connect the VPN with nmcli connection up VPN it succeceds. But if I bring the interface down and trying to bring it up again it fails. If I restart the raspberry I can connect to VPN again. What is the next step? Do you guys have any idea what has gone wrong?
In the journalctl log I get this message when it fails:
Could not determine IPv4/IPv6 protocol
Oct 23 15:56:24 raspberrypi nm-openvpn[2282]: SIGUSR1[soft,init_instance] received, process restarting
Oct 23 15:56:29 raspberrypi nm-openvpn[2282]: WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
Oct 23 15:56:29 raspberrypi nm-openvpn[2282]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Oct 23 15:56:29 raspberrypi nm-openvpn[2282]: RESOLVE: Cannot resolve host address: vpn.******.**:1194 (Name or service not known)
Oct 23 15:56:29 raspberrypi nm-openvpn[2282]: RESOLVE: Cannot resolve host address: vpn.*****.**:1194 (Name or service not known).
pi#raspberrypi:~ $ openvpn --version
OpenVPN 2.4.7 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 20 2019
library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10
uname -a
Linux raspberrypi 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux
NetworkManager --version
1.14.6
I'm getting some errors when I start salt minions:
Error while bringing up minion for multi-master. Is master at salt-server00001.nix.us.companyworld.company.com responding?
2019-10-16 11:57:27,935 [salt.minion ][ERROR ][34679] Error while bringing up minion for multi-master. Is master at usazrcncm10286.nix.us.kworld.kpmg.com responding?
2019-10-16 11:57:37,990 [salt.crypt ][ERROR ][34679] The masters sent its public-key signature, but signature verification is not enabled on the minion. Either enable signature verification on the minion or disable signing the public key on the master!
2019-10-16 11:57:37,990 [salt.crypt ][CRITICAL][34679] The Salt Master server's public key did not authenticate!
The master may need to be updated if it is a version of Salt lower than 2017.7.2, or
If you are confident that you are connecting to a valid Salt Master, then remove the master public key and restart the Salt Minion.
I am NOT setting up multi-master.
I have accepted the key for the server on the salt master.
I've opened up the salt ports on the firewall.
But the salt server still isn't responding.
This is my salt versions report:
salt --versions-report
Salt Version:
Salt: 2018.3.4
Dependency Versions:
cffi: Not Installed
cherrypy: unknown
dateutil: Not Installed
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
Jinja2: 2.8.1
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.4.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 2.7.13 (default, Mar 30 2018, 15:31:59)
python-gnupg: Not Installed
PyYAML: 3.11
PyZMQ: 18.0.1
RAET: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 4.3.1
System Versions:
dist: redhat 6.10 Santiago
locale: UTF-8
machine: x86_64
release: 2.6.32-754.2.1.el6.x86_64
system: Linux
version: Red Hat Enterprise Linux Server 6.10 Santiago
Why am I seeing this problem and how do I correct it?
Look for errors in the /var/log/salt/minion
Then, issue salt '*' service.status and check if the master is running.
Do a check of the salt-master service systemctl status salt-master
In my case, the salt-master failed to start:
● Salt-master.service - The Salt Master Server
Loaded: loaded (/usr/lib/systemd/system/salt-master.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/salt-master.service.d
└─salt-master-opts-managed.conf
Active: failed (Result: timeout) since Wed 2020-07-08 10:59:22 -03; 54min ago
Docs: man:salt-master(1)
file:///usr/share/doc/salt/html/contents.html
https://docs.saltstack.com/en/latest/contents.html
Process: 5780 ExecStart=/usr/bin/salt-master (code=killed, signal=TERM)
Main PID: 5780 (code=killed, signal=TERM)
Jul 08 10:57:52 v321p601 systemd[1]: Starting The Salt Master Server...
Jul 08 10:58:26 v321p601 salt-master[5780]: [INFO ] Setting up the Salt Master
Jul 08 10:59:22 v321p601 systemd[1]: salt-master.service start operation timed out. Terminating.
Jul 08 10:59:22 v321p601 systemd[1]: Failed to start The Salt Master Server.
Jul 08 10:59:22 v321p601 systemd[1]: Unit salt-master.service entered failed state.
Jul 08 10:59:22 v321p601 systemd[1]: salt-master.service failed.
Try restarting the service with systemctl start salt-master.
If the error persists, run netstat -lnp on the master and see if the Salt ports are there and listening.
In my case, I've reissued the command to start the salt-master service after a while and it went online:
● salt-master.service - The Salt Master Server
Loaded: loaded (/usr/lib/systemd/system/salt-master.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/salt-master.service.d
└─salt-master-opts-managed.conf
Active: active (running) since Wed 2020-07-08 12:19:31 -03; 4min 55s ago
Docs: man:salt-master(1)
file:///usr/share/doc/salt/html/contents.html
https://docs.saltstack.com/en/latest/contents.html
Main PID: 27609 (salt-master)
CGroup: /system.slice/salt-master.service
├─27609 /usr/bin/python /usr/bin/salt-master
├─27618 /usr/bin/python /usr/bin/salt-master
├─27820 /usr/bin/python /usr/bin/salt-master
├─27824 /usr/bin/python /usr/bin/salt-master
├─27839 /usr/bin/python /usr/bin/salt-master
├─27840 /usr/bin/python /usr/bin/salt-master
├─27841 /usr/bin/python /usr/bin/salt-master
├─27842 /usr/bin/python /usr/bin/salt-master
├─27849 /usr/bin/python /usr/bin/salt-master
├─27850 /usr/bin/python /usr/bin/salt-master
├─27851 /usr/bin/python /usr/bin/salt-master
├─27852 /usr/bin/python /usr/bin/salt-master
└─27853 /usr/bin/python /usr/bin/salt-master
Jul 08 12:21:14 v321p601 salt-master[27609]: [INFO ] Authentication accepted from 4b11df09-8c57-4745-ac5a-1ab3da854566
Jul 08 12:21:14 v321p601 salt-master[27609]: [INFO ] Authentication request from eeea44c1-5d2e-430d-8217-50f2517e587b
Jul 08 12:21:14 v321p601 salt-master[27609]: [INFO ] Authentication accepted from eeea44c1-5d2e-430d-8217-50f2517e587b
Jul 08 12:21:14 v321p601 salt-master[27609]: [INFO ] Authentication request from 48892d9e-78b1-43c2-a0d4-479ac4907432
Jul 08 12:21:14 v321p601 salt-master[27609]: [INFO ] Authentication accepted from 48892d9e-78b1-43c2-a0d4-479ac4907432
Jul 08 12:21:14 v321p601 salt-master[27609]: [INFO ] Got return from 70a62d5b-31df-403d-b0f5-3e90d1b9fd7d for job 20200708122114319236
Jul 08 12:21:18 v321p601 salt-master[27609]: [INFO ] Authentication request from 39f50b14-89d4-427b-bd46-39b11cada7da
Jul 08 12:21:27 v321p601 salt-master[27609]: [INFO ] Authentication request from 81f9b89c-a7d3-4264-b156-f2b0470590c3
Jul 08 12:21:27 v321p601 salt-master[27609]: [INFO ] Authentication accepted from 39f50b14-89d4-427b-bd46-39b11cada7da
Jul 08 12:21:27 v321p601 salt-master[27609]: [INFO ] Authentication accepted from 81f9b89c-a7d3-4264-b156-f2b0470590c3
References:
saltstack cheatsheet
saltmaster not running properly?
my rstudio server was hanging too often while loading starting r shiny app. So after googling around i tried to stop and start the rstudio server again. i also tried to kill all process running on 8787 port. But had no luck solving the issue. now r studio server keeps waiting while opening on web browser.
I have used below command to kill process running on 8787 port. after running the command there was no result.
sudo kill -TERM 20647
(20647 is port where rserver process is listening. i got this port number after running 'sudo netstat -ntlp | grep :8787' command).
to stop and restart r studio server, i used below command
sudo rstudio-server stop
sudo rstudio-server start
expected result is working sr studio server which doesnt hang while loading shiny app.
after running status command i found below error logged for rstudio server.
rstudio-server.service - RStudio Server
Loaded: loaded (/etc/systemd/system/rstudio-server.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Wed 2019-08-28 04:50:07 CDT; 11s ago
Process: 31611 ExecStop=/usr/bin/killall -TERM rserver (code=exited, status=0/SUCCESS)
Process: 31609 ExecStart=/usr/lib/rstudio-server/bin/rserver (code=exited, status=0/SUCCESS)
Main PID: 31610 (code=exited, status=1/FAILURE)
CGroup: /system.slice/rstudio-server.service
└─20647 /usr/lib/rstudio-server/bin/rserver
Aug 28 04:50:07 nds-vm1.novalocal systemd[1]: Unit rstudio-server.service entered failed state.
Aug 28 04:50:07 nds-vm1.novalocal systemd[1]: rstudio-server.service failed.
Aug 28 04:50:07 nds-vm1.novalocal systemd[1]: rstudio-server.service holdoff time over, scheduling r...rt.
Aug 28 04:50:07 nds-vm1.novalocal systemd[1]: Stopped RStudio Server.
Aug 28 04:50:07 nds-vm1.novalocal systemd[1]: start request repeated too quickly for rstudio-server....ice
Aug 28 04:50:07 nds-vm1.novalocal systemd[1]: Failed to start RStudio Server.
Aug 28 04:50:07 nds-vm1.novalocal systemd[1]: Unit rstudio-server.service entered failed state.
Aug 28 04:50:07 nds-vm1.novalocal systemd[1]: rstudio-server.service failed.
As a last resort, i have restarted my VM where i am running r-studio server. It seems to have resolved my issue.
I am installing Apache cloudstack on ubuntu 16.0.4, but after installing cloudstack setup when I start services of cloudstack management service it displayed the following errors. (I have installed tomcat7, but tomcat 6 is not installed)
Warning: cloudstack-management.service changed on disk. Run 'systemctl daemon-reload' to reload units. Job for
cloudstack-management.service failed because the control process
exited with error code. See "systemctl status
cloudstack-management.service" and "journalctl -xe" for details.
I have checked systemctl status cloudstack-management.service command and it displays the following:
cloudstack-management.service - LSB: Start Tomcat (CloudStack).
Loaded: loaded (/etc/init.d/cloudstack-management; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-08-25 21:53:07 IST; 1min 11s ago
Docs: man:systemd-sysv-generator(8)
Process: 26684 ExecStart=/etc/init.d/cloudstack-management start (code=exited, status=1/FAILURE)
Aug 25 21:53:07 dhaval-pc systemd[1]: Starting LSB: Start Tomcat (CloudStack)....
Aug 25 21:53:07 dhaval-pc cloudstack-management[26684]: * cloudstack-management is not installed
Aug 25 21:53:07 dhaval-pc systemd[1]: cloudstack-management.service: Control process exited, code=exited status=1
Aug 25 21:53:07 dhaval-pc systemd[1]: Failed to start LSB: Start Tomcat (CloudStack)..
Aug 25 21:53:07 dhaval-pc systemd[1]: cloudstack-management.service: Unit entered failed state.
Aug 25 21:53:07 dhaval-pc systemd[1]: cloudstack-management.service: Failed with result 'exit-code'.
Warning: cloudstack-management.service changed on disk. Run 'systemctl daemon-reload' to reload units.
What change can I make in vi /etc/init.d/cloudstack-management file?
Starting the example cordapp on Ubuntu as a service per: https://docs.corda.net/releases/release-V3.1/deploying-a-node.html
On running the node I get the following error:
Apr 25 17:48:04 single-node-marketplace-master systemd[1]: Started Cordapp Example - party B.
Apr 25 17:48:22 single-node-marketplace-master java[99477]: Exception in thread "main" java.io.IOException: Permission denied
Apr 25 17:48:22 single-node-marketplace-master java[99477]: at java.io.UnixFileSystem.createFileExclusively(Native Method)
Apr 25 17:48:22 single-node-marketplace-master java[99477]: at java.io.File.createNewFile(File.java:1012)
Apr 25 17:48:22 single-node-marketplace-master java[99477]: at net.corda.node.internal.NodeStartup.enforceSingleNodeIsRunning(NodeStartup.kt:226)
Apr 25 17:48:22 single-node-marketplace-master java[99477]: at net.corda.node.internal.NodeStartup.run(NodeStartup.kt:53)
Apr 25 17:48:22 single-node-marketplace-master java[99477]: at net.corda.node.Corda.main(Corda.kt:13)
The Cordapp is being started as the "corda" user. Ensure that you've both created the user and set the permission in /opt/<cordapp name>
sudo adduser --system --no-create-home --group corda
sudo chown corda:corda /opt/partyB