Hello.
Help me please with this problem:
I set the COS in the virtual machine, access to the Internet only through the proxy. Tell me where to register the data of the external proxy to the installation, COS was able to register?
Help me please with this problem:
I set the COS in the virtual machine, access to the Internet only through the proxy. Tell me where to register the data of the external proxy to the installation, COS was able to register?
In Installation
Share this post:
Responses (8)
-
Accepted Answer
cat /var/lib/syswatch/state
SYSWATCH_WANIF=""
SYSWATCH_WANOK=""
Very interesting...this is bad. Can you post output from:
cat /etc/clearos/network.conf | grep IF
It will tell us if there is a bug or a configuration issue.
RE: Proxy/Yum...I can duplicate this issue.....looks like yum in CentOS7 is not respecting the proxy global environment settings. We will have to investigate further, but an easy work around is to edit /etc/yum.conf and add to the bottom of that file:
proxy=http://192.168.1.1:3128
proxy_username=someuser
proxy_password=somepw
Where 192.168.1.1 is replaced with your server's proxy and the someuser/somepw is a user/password combo that has access to the proxy.
B -
Accepted Answer
COS 7.1
cat /var/lib/syswatch/state
SYSWATCH_WANIF=""
SYSWATCH_WANOK=""
ifconfig
ens18: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.14.4.161 netmask 255.255.0.0 broadcast 10.14.255.255
inet6 fe80::42:e4ff:fe7a:cea8 prefixlen 64 scopeid 0x20<link>
ether 02:42:e4:7a:ce:a8 txqueuelen 1000 (Ethernet)
RX packets 10470 bytes 1838030 (1.7 MiB)
RX errors 0 dropped 149 overruns 0 frame 0
TX packets 2151 bytes 1766423 (1.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens19: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.99.1.2 netmask 255.255.255.0 broadcast 10.99.1.255
inet6 fe80::ac02:e8ff:fe8e:ce44 prefixlen 64 scopeid 0x20<link>
ether ae:02:e8:8e:ce:44 txqueuelen 1000 (Ethernet)
RX packets 712 bytes 190829 (186.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 404 bytes 115317 (112.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 304 bytes 26780 (26.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 304 bytes 26780 (26.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
service syswatch status
syswatch.service - SYSV: This daemon keeps an eye on your Internet connection and other critical systems.
Loaded: loaded (/etc/rc.d/init.d/syswatch)
Active: active (running) since Thu 2015-12-03 14:27:30 MSK; 14min ago
Process: 4651 ExecReload=/etc/rc.d/init.d/syswatch reload (code=exited, status=0/SUCCESS)
Process: 2277 ExecStart=/etc/rc.d/init.d/syswatch start (code=exited, status=0/SUCCESS)
Main PID: 2281 (syswatch)
CGroup: /system.slice/syswatch.service
└─2281 syswatc
Dec 03 14:27:30 localhost.localdomain syswatch[2277]: Starting syswatch: [ OK ]
Dec 03 14:27:30 localhost.localdomain systemd[1]: Started SYSV: This daemon keeps an eye on your Internet connection and other critical systems..
Dec 03 14:27:59 localhost.localdomain systemd[1]: Reloading SYSV: This daemon keeps an eye on your Internet connection and other critical systems.
.
Dec 03 14:27:59 localhost.localdomain syswatch[2505]: /etc/rc.d/init.d/syswatch: line 18: [: =: unary operator expected
Dec 03 14:27:59 localhost.localdomain syswatch[2505]: Reloading syswatch: [ OK ]
Dec 03 14:27:59 localhost.localdomain systemd[1]: Reloaded SYSV: This daemon keeps an eye on your Internet connection and other critical systems..
Dec 03 14:34:24 localhost.localdomain systemd[1]: Reloading SYSV: This daemon keeps an eye on your Internet connection and other critical systems.
.
Dec 03 14:34:24 localhost.localdomain syswatch[4651]: /etc/rc.d/init.d/syswatch: line 18: [: =: unary operator expected
Dec 03 14:34:24 localhost.localdomain syswatch[4651]: Reloading syswatch: [ OK ]
Dec 03 14:34:24 localhost.localdomain systemd[1]: Reloaded SYSV: This daemon keeps an eye on your Internet connection and other critical systems..
I manually set in the file /var/lib/syswatch/state
SYSWATCH_WANIF="ens18"
SYSWATCH_WANOK="ens18"
performed
service syswatch reload
and installation went on, but now stuck at the stage of checking for updates. It seems to me that the upstream_proxy does not work or does not work properly. -
Accepted Answer
-
Accepted Answer
Andy,
I can think of about 3 reports we've had via support of users saying they are in the loop between the Registration page and bouncing back to the Network settings page. So far, I haven't been able to duplicate or remote login to someone who has this issue, but I'd love to track it down.
If interested, let's take this private...please create a support ticket here and address it to me (Ben) and we'll get you up and running on 7...no charge, of course...you'd be doing us a favour by providing access to your system in an environment/situation we cannot duplicate.
B -
Accepted Answer
I'm a little hasty when he wrote that everything works.
In 6.6 I was able to create account, install went fine, Marketplace works too, but there is no access to the Internet. On the tab "IP Setting":
Network Status
Gateway Status Connected
Internet Status Offline
DNS Lookup Connected.
Amazing!
When installing 7.1 I also managed to create account , by then I get a warning that it is necessary to check the network settings on the installation and does not go.
I'm ready for another fight with the 7.1, but what to do to install went on I do not know.
With that in 6.6 I have access to the web interface from two ip address (internal and external), and when I put 7.1 I can only go on the external.
Do you have any ideas? -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
There's an app in the repos (doesn't show up in Marketplace) that you can install:
yum install app-upstream-proxy
Once installed, you can configure it via Webconfig...I think it shows up under Network category...not 100% sure on that.
This app is beta, but it should work for you.... Feedback welcome.
B
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »