I am using puppet6 on centos 7.4.
$ puppet config pring confdir
is pointing to incorrect folder. I tried setting it to right folder but
set command does not have any effect. any clue what is happening?
Related
I am new to Golang, I am following this tutorial https://golang.org/doc/tutorial/getting-started but for some reason I keep getting this message every time I try to run the code:
$GOPATH/go.mod exists but should not
I have tried to look at answers like this one: https://stackoverflow.com/a/62062562/9785222 but I dont understand what is GOPATH and where is it.
I am using Vi as an editor on Linux Fedora
GOPATH defaults to $HOME/go on Unix.
Remove the file $HOME/go/go.mod or explicitly set $GOPATH to a different directory.
$GOPATH should point out to the src directory, in my case in Debian, I set $GOPATH to /usr/local/go/src and the problem was solved.
export $GOPATH=/usr/local/go/src
What is GOPATH ?
GOPATH is a variable that defines a folder, under which GO expects our code to reside . For more details, you can check this link
I am working with centos 6.9 . I unconsciously deleted the ssh_config file which is located in /etc/ssh.
Any idea please to restore it , or to rewrite it?
Thanks a lot
I just installed lsyncd-2.1.5 on a CentOS 6.4 server. I was able to run make and make install on the distribution to compile the daemon. I was able to setup the following configure file at /etc/lsyncd.lua. I was able to setup the daemon file at /etc/init.d/lsyncd. I was also able to setup the logs correctly. However, when I go to run start command on lsyncd, it throws the error:
/bin/bash: line 1: Illegal Insruction /usr/local/bin/lsyncd -pidfile /var/run/lsyncd.pid /etc/lsyncd.lua
I checked at /var/run for the file lsyncd.pid and this file was not created by lsyncd.
Any thoughts on what I should do here? Can I get this file created? Do I have to reinstall?
Let me know if I can provide any further information.
Here is what I did to solve this issue. I removed all instances of my lsyncd distribution. I had previously downloaded and compiled my package in the folder /var/tmp, so I now navigated to the root folder and ran my download command here. I un-tarred the package, and compiled the package in the root folder and setup all of my configuration files. After I started the service now, the lsyncd.pid file was now in the /var/run folder. Very strange. Can anyone tell me what the difference is between compiling in the root or /var/tmp?
Or is this possibly a situation where something possibly went wrong the first time around? Does anyone have any insight on this?
I am trying to automate installation of CentOS 6.4 -minimal with kickstart on a DVD
Below is my kick start that was auto generated by anaconda
# Kickstart file automatically generated by anaconda.
#version=DEVEL
install
cdrom
lang en_US.UTF-8
keyboard us
network --onboot no --device eth0 --bootproto dhcp --noipv6
rootpw --iscrypted $6$.tHtXJMs5GEzyQRm$52EX5ue3UuFC/zgencUbxuvwHXIPDuLmllkuNs4NRq7/Wa7FsI8ICxwPDsy/KnzSaUfEqfBROLAv0tPMksOhA1
firewall --service=ssh
authconfig --enableshadow --passalgo=sha512
selinux --enforcing
timezone --utc America/New_York
bootloader --location=mbr --driveorder=sda --append="crashkernel=auto rhgb quiet"
repo --name="CentOS" --baseurl=cdrom:sr0 --cost=100
%packages --nobase
#core
%end
============================================================
The problem happens when the ks.cfg tries to install packages from Repo that is in DVD
The error I'm getting:
Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated.
cannot find a valid baseurl for repo:CentOS
============================================================
If this a bug, is there any other way to automate the installation ?
Is there any alternate solution to Automate the CentOS6.4 minimal?
I have tried removing the line
repo --name="CentOS" --baseurl=cdrom:sr0 --cost=100
Problem still persists
Then I tried changing to something like this
repo --name="CentOS" --baseurl=file:///mnt/source--cost=100
Problem still persists
What am i missing to include .... ???
I've faced the same problem today, but after commenting the line it worked :)
#repo --name="CentOS" --baseurl=cdrom:sr1 --cost=100
Why don't you use system-config-kickstart gui tool for creating your own file and then use mkisofs to create your own iso too.
http://www.centos.org/docs/4/html/rhel-sag-en-4/ch-redhat-config-kickstart.html
The above link would be helpful.
Thanks & Regards,
Alok Thaker
From the RHEL 7 Kickstart documentation:
url Install from an installation tree on a remote server via FTP, HTTP, or HTTPS.
--url= - The location to install from. Supported protocols are HTTP, HTTPS, FTP, and file.
--mirrorlist= - The mirror URL to install from.
--proxy= - Specify an HTTP, HTTPS or FTP proxy to use while performing the installation.
--noverifyssl - Disable SSL verification when connecting to an HTTPS server.
You have to set url property, like:
url --url=http://mirror.centos.org/centos/7.0.1406/os/x86_64/
There are a handful of Packer templates that leverages kickstart scripts to create Centos VMs. One of those is the Bento Project.
You did not have a space between the second and third parameter:
repo --name="CentOS" --baseurl=file:///mnt/source/--cost=100
Correct:
repo --name="CentOS" --baseurl=file:///mnt/source/ --cost=100
I need to update Apache Ant on my server.
I downloaded the newest Ant, built it, and (I thought) installed it. But when when I check it says the old version is still installed.
How do I update/replace the previous version of Apache Ant on a CentOS 5.? server?
take care,
lee
As mentioned it's probably getting picked up in your path. Post the output from echo $PATH
To configure your CentOS after installing a new version of Apache Ant, proceed to the following steps:
Locate the directory where the new Ant is located
Set the ANT_HOME environment variable to this directory
Add $ANT_HOME/bin to your PATH
P.S. To modify environment variables, you may edit the /etc/environment file, and reboot, or modify your local .bashrc. Look at your current environment variables by analyzing the output of printenv, e.g., to see the current value of PATH and then add the Ant path to it, e.g.
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/jvm/adoptopenjdk-8-hotspot-amd64/bin:/usr/local/ant/bin