cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
manix
Monday
  • 12 Posts
  • 0 Likes Given
  • 0 Solutions
  • 0 Likes Received

Re: SAS consul and postgres errors

by Calcite | Level 5 in Administration and Deployment
a week ago
a week ago
UPDATE:   After a while, ip neigh | grep 172.16.18.70  was showing a STALE status and after that REACHABLE.   I was able to restart SAS and now is running.   Thank you very much for the support! ... View more

Re: SAS consul and postgres errors

by Calcite | Level 5 in Administration and Deployment
2 weeks ago
2 weeks ago
I should mention that SAS is configured on a cluster so I don't know if the virtual IP shoul be assigned to that particular node. All commands from from the documentation give some kind of error:   [root@sas1 pgpool0]# nslookup 172.16.18.70 ** server can't find 70.18.16.172.in-addr.arpa.: NXDOMAIN [root@sas1 pgpool0]# arping -c 3 172.16.18.70 arping: Suitable device could not be determined. Please, use option -I. Usage: arping [-fqbDUAV] [-c count] [-w timeout] [-I device] [-s source] destination -f : quit on first reply -q : be quiet -b : keep broadcasting, don't go unicast -D : duplicate address detection mode -U : Unsolicited ARP mode, update your neighbours -A : ARP answer mode, update your neighbours -V : print version and exit -c count : how many packets to send -w timeout : how long to wait for a reply -I device : which ethernet device to use -s source : source ip address destination : ask for what ip address [root@sas1 pgpool0]# arping -I eth0 172.16.18.70 arping: Device eth0 not available. [root@sas1 pgpool0]# arping -I bond0 172.16.18.70 ARPING 172.16.18.70 from 172.16.18.44 bond0 ^CSent 189 probes (189 broadcast(s)) Received 0 response(s) [root@sas1 pgpool0]# ipneigh grep 172.16.18.70 bash: ipneigh: command not found... [root@sas1 pgpool0]# ip neigh grep 172.16.18.70 Command "grep" is unknown, try "ip neigh help". [root@sas1 pgpool0]# ip neigh | grep 172.16.18.70 172.16.18.70 dev bond0 FAILED [root@sas1 pgpool0]# arp -a | grep 172.16.18.70 ? (172.16.18.70) at <incomplete> on bond0 [root@sas1 pgpool0]# ifconfig | egrep 'RUNNING|broadcast|Ethernet' bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500 inet 172.16.18.44 netmask 255.255.255.0 broadcast 172.16.18.255 ether 38:68:dd:1f:44:50 txqueuelen 1000 (Ethernet) bond0:0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500 inet 172.16.18.71 netmask 255.255.255.255 broadcast 0.0.0.0 ether 38:68:dd:1f:44:50 txqueuelen 1000 (Ethernet) bond1: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500 inet 172.16.18.45 netmask 255.255.255.0 broadcast 172.16.18.255 ether b0:26:28:f7:97:25 txqueuelen 1000 (Ethernet) eno1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 38:68:dd:1f:44:50 txqueuelen 1000 (Ethernet) eno2: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 38:68:dd:1f:44:50 txqueuelen 1000 (Ethernet) ens1f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether b0:26:28:f7:97:24 txqueuelen 1000 (Ethernet) ens1f1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether b0:26:28:f7:97:25 txqueuelen 1000 (Ethernet) lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:30:ae:1e txqueuelen 1000 (Ethernet) [root@sas1 pgpool0]# ip addr | egrep 'LOWER_UP|link/ether|inet ' 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 inet 127.0.0.1/8 scope host lo 2: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 38:68:dd:1f:44:50 brd ff:ff:ff:ff:ff:ff 3: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether b0:26:28:f7:97:24 brd ff:ff:ff:ff:ff:ff 4: ens1f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000 link/ether b0:26:28:f7:97:25 brd ff:ff:ff:ff:ff:ff 5: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 38:68:dd:1f:44:50 brd ff:ff:ff:ff:ff:ff 7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 38:68:dd:1f:44:50 brd ff:ff:ff:ff:ff:ff inet 172.16.18.44/24 brd 172.16.18.255 scope global bond0 inet 172.16.18.71/32 scope global bond0:0 8: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether b0:26:28:f7:97:25 brd ff:ff:ff:ff:ff:ff inet 172.16.18.45/24 brd 172.16.18.255 scope global bond1 link/ether 52:54:00:30:ae:1e brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 link/ether 52:54:00:30:ae:1e brd ff:ff:ff:ff:ff:ff link/ether 3a:68:dd:1f:44:57 brd ff:ff:ff:ff:ff:ff ... View more

Re: SAS consul and postgres errors

by Calcite | Level 5 in Administration and Deployment
2 weeks ago
2 weeks ago
the service is running: ./sas-viya-sasdatasvrc-postgres-pgpool0-consul-template-operation_node status ./sas-viya-sasdatasvrc-postgres-pgpool0-consul-template-operation_node sourcing sds_set_env_variable with /opt/sas/viya/config/etc/sasdatasvrc/postgres/pgpool0/sds_env_var.sh... SAS_HOSTNAME=sas1.onrc.ro, SAS_SERVICE_ADDR=sas1.onrc.ro, SAS_BIND_ADDR=172.16.18.44 VAULT_ADDR: https://sas3.onrc.ro:8200 SASCONFIG=/opt/sas/viya/config, PGHOME=/opt/sas/viya/home/postgresql11, PGPOOLHOME=/opt/sas/viya/home/pgpool-II40 POSTGRES_FULL_VERSION=11.9, PGPOOL_FULL_VERSION=4.0.6 Sourced. HA_PGPOOL_COUNT=3, SASCONFIG=/opt/sas/viya/config, SAS_LOG_DIR=/opt/sas/viya/config/var/log Service sas-viya-sasdatasvrc-postgres-pgpool0-consul-template-operation_node is running with PID 202254.     this, i think is where the virtual IP and other parameters are defined: cat /opt/sas/viya/config/etc/sasdatasvrc/postgres/pgpool0/sds_env_var.sh export CONSUL_PORT="8500" export DEFAULT_POSTGRES_SERVICE="postgres" export INSTALL_GROUP="sas" export INSTALL_USER="sas" export INVENTORY_HOSTNAME="casactive" export SASCONFIG="/opt/sas/viya/config/etc/sasdatasvrc" export SASHOME="/opt/sas/viya/home" export SAS_LOG_DIR="/opt/sas/viya/config/var/log/sasdatasvrc" export HA_PGPOOL_VIRTUAL_IP=172.16.18.70 export HA_PGPOOL_WATCHDOG_PORT=5433 export PCP_PORT=5430 export PERMS_OVERRIDE=false export PGPOOL_PORT=5431 export POOL_NUMBER=0 export SANMOUNT=/opt/sas/viya/config/data/sasdatasvrc export SERVICE_NAME=postgres   In the same folder i have the watchdog output file: cat pcp_watchdog_info.out ERROR: connection to host "172.16.18.70" failed with error "No route to host" ... View more

Re: SAS consul and postgres errors

by Calcite | Level 5 in Administration and Deployment
2 weeks ago
2 weeks ago
the log gives the same error:  failed 'f_operate_node_request PoolNode:All:Stop'. rC=1 ERROR: f_operate_node_request: The consul-template-operation-node service may be down or failed to invoke its template script. node: pgpool0, wait time=16s 2025-12-16 12:15:37.697 LOG: f_read_kv_to_var: /opt/sas/viya/home/bin/sas-bootstrap-config kv read config/postgres/admin/pgpool2/operation_status 2025-12-16 12:15:37.928 LOG: f_read_kv_to_var: config/postgres/admin/pgpool2/operation_status=Successful 2025-12-16 12:15:37.943 LOG: f_operate_node_request: f_release_lock CurrentLockNodeOperation 2025-12-16 12:15:37.958 LOG: f_release_lock: f_assert_env AnyTypeNode sas 2025-12-16 12:15:37.973 LOG: f_release_lock: Release lock: /opt/sas/viya/home/bin/sas-bootstrap-config kv lock release --key config/postgres/session/CurrentLockNodeOperation --session-id f08b016d-cbd0-9265-6757-9392118acad4 true 2025-12-16 12:15:38.237 LOG: f_release_lock: Released the Consul lock 2025-12-16 12:15:38.252 LOG: f_delete_lock_session: f_assert_env AnyTypeNode sas 2025-12-16 12:15:38.266 LOG: f_delete_lock_session: Delete session: /opt/sas/viya/home/bin/sas-bootstrap-config session delete --id f08b016d-cbd0-9265-6757-9392118acad4 2025-12-16 12:15:38.545 LOG: f_delete_lock_session: Consul lock session f08b016d-cbd0-9265-6757-9392118acad4 was deleted 2025-12-16 12:15:38.555 ERROR: f_operate_node_request: Failed PoolNode:All:Stop for postgres 2025-12-16 12:15:38.564 ERROR: f_stop_cluster: failed 'f_operate_node_request PoolNode:All:Stop'. rC=1 ERROR: f_operate_node_request: The consul-template-operation-node service may be down or failed to invoke its template script. node: pgpool0, wait time=16s ERROR: f_operate_node_request: Failed PoolNode:All:Stop for postgres ERROR: f_stop_cluster: failed 'f_operate_node_request PoolNode:All:Stop'. rC=1 2025-12-16 12:15:38.574 ERROR: main: failed 'f_stop_cluster'. rC=1   The virtual IP address is set somewhere in the pgpool config files ? Can it be modified? I tried to restart pgpool and postgresql services but the same error appears.   ... View more

SAS consul and postgres errors

by Calcite | Level 5 in Administration and Deployment
2 weeks ago
2 weeks ago
Hello, I am having problems restarting SAS services. Could be a postgres/ consul issue or is it a network issue? Thank you in advance. ... View more

Can't start SAS services

by Calcite | Level 5 in Administration and Deployment
2 weeks ago
2 weeks ago
Hello, after I received a 500 error on login I tried to restart SAS. I have the following error:   fatal: [casactive]: FAILED! => {"changed": true, "msg": "non-zero return code", "rc": 1, "stderr": "Shared connection to sas1 closed.\r\n", "stderr_lines": ["Shared connection to sas1 closed."], "stdout": "ERROR: f_get_pool_primary_from_watchdog: Failed '/opt/sas/viya/home/pgpool-II40/bin/pcp_watchdog_info -h 172.16.18.70 -p 5430 -U sas with sas password'. return_code: 1. Virtual IP may not be accessible. Check 'ping 172.16.18.70' from the current host\r\nERROR: f_show_pool_nodes: failed 'f_set_psql_to_pool_primary'. rC=2\r\nCurrentLogFile=/opt/sas/viya/config/var/log/sasdatasvrc/postgres/pgpool0/shutdownall_20251216_121506_668.log\r\nTo see the progress, do: tail -f <log-file>\r\nERROR: f_operate_node_request: The consul-template-operation-node service may be down or failed to invoke its template script. node: pgpool0, wait time=16s\r\nERROR: f_operate_node_request: Failed PoolNode:All:Stop for postgres\r\nERROR: f_stop_cluster: failed 'f_operate_node_request PoolNode:All:Stop'. rC=1\r\nERROR: main: failed 'f_stop_cluster'. rC=1\r\n", "stdout_lines": ["ERROR: f_get_pool_primary_from_watchdog: Failed '/opt/sas/viya/home/pgpool-II40/bin/pcp_watchdog_info -h 172.16.18.70 -p 5430 -U sas with sas password'. return_code: 1. Virtual IP may not be accessible. Check 'ping 172.16.18.70' from the current host", "ERROR: f_show_pool_nodes: failed 'f_set_psql_to_pool_primary'. rC=2", "CurrentLogFile=/opt/sas/viya/config/var/log/sasdatasvrc/postgres/pgpool0/shutdownall_20251216_121506_668.log", "To see the progress, do: tail -f <log-file>", "ERROR: f_operate_node_request: The consul-template-operation-node service may be down or failed to invoke its template script. node: pgpool0, wait time=16s", "ERROR: f_operate_node_request: Failed PoolNode:All:Stop for postgres", "ERROR: f_stop_cluster: failed 'f_operate_node_request PoolNode:All:Stop'. rC=1", "ERROR: main: failed 'f_stop_cluster'. rC=1"]}   I have restarted the postgres service and the consul template operation service manually but without any result. I don't think is a network issue.   ... View more

tmp folder space error

by Calcite | Level 5 in Administration and Deployment
‎10-13-2025 04:20 AM
‎10-13-2025 04:20 AM
Hello, I have the following when trying to start/stopping SAS: TASK [Check the accessibility of the hosts] ************************************************************************************************************************************************ ok: [casactive] ok: [compute] fatal: [caspassive]: UNREACHABLE! => {"changed": false, "msg": "mkdir: cannot create directory ‘/tmp/.root.ansible’: No space left on device\n", "unreachable": true}   I have enough space on the partition which contains the tmp folder.(around 18 GB free space) Also I can see the /tmp/.root.ansible folder. Is it a space issue or should I look for something else?     ... View more

Re: error at login in SAS

by Calcite | Level 5 in Administration and Deployment
‎09-23-2025 03:42 AM
‎09-23-2025 03:42 AM
It worked.Thank you very much! ... View more

Re: error at login in SAS

by Calcite | Level 5 in Administration and Deployment
‎09-22-2025 05:35 AM
‎09-22-2025 05:35 AM
IT seems to be a certificate issue: in the logs from the folder /opt/sas/viya/config/var/log/saslogon/default i have the following error:   Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:450) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:317) at sun.security.validator.Validator.validate(Validator.java:262) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:330) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:237) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:132) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1670) ... 158 common frames omitted Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:445)   The certificate was installed this week. Maybe it saw not installed correctly/at the correct location? ... View more

error at login in SAS

by Calcite | Level 5 in Administration and Deployment
‎09-17-2025 09:33 AM
‎09-17-2025 09:33 AM
Hello, i have the the following error when trying to ligin into SAS: 500 Internal Server Error An error occurred. Please contact your system administrator. I tried to restart SAS(using the command ansible-playbook viya-ark/playbooks/viya-mmsu/viya-services-start.yml)   but the same error appears.   I looked into a elastic search  log :   [2025-09-17T14:13:05,657][WARN ][o.e.t.OutboundHandler ] [yDJPxQE] send message failed [channel: Netty4TcpChannel{localAddress=0.0.0.0/0.0.0.0:9300, remoteAddress=/172.16.18.42:45028}] java.nio.channels.ClosedChannelException: null at io.netty.channel.AbstractChannel$AbstractUnsafe.write(...)(Unknown Source) ~[?:?] [2025-09-17T14:13:05,667][WARN ][o.e.c.NodeConnectionsService] [yDJPxQE] failed to connect to node {sRvANwN}{sRvANwN4RNK70-zh2C2VLw}{rnTpgYXvSBum2U_4dEQQ5Q}{sas3.onrc.ro}{172.16.18.42:9300} (tried [1] times) org.elasticsearch.transport.ConnectTransportException: [sRvANwN][172.16.18.42:9300] connect_exception at org.elasticsearch.transport.TcpTransport$ChannelsConnectedListener.onFailure(TcpTransport.java:1309) ~[elasticsearch-6.8.6.jar:6.8.6] at org.elasticsearch.action.ActionListener.lambda$toBiConsumer$2(ActionListener.java:100) ~[elasticsearch-6.8.6.jar:6.8.6] at org.elasticsearch.common.concurrent.CompletableContext.lambda$addListener$0(CompletableContext.java:42) ~[elasticsearch-core-6.8.6.jar:6.8.6] at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774) ~[?:1.8.0_262] at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750) ~[?:1.8.0_262] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488) ~[?:1.8.0_262] at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1990) ~[?:1.8.0_262] at org.elasticsearch.common.concurrent.CompletableContext.completeExceptionally(CompletableContext.java:57) ~[elasticsearch-core-6.8.6.jar:6.8.6] at org.elasticsearch.transport.netty4.Netty4TcpChannel.lambda$new$1(Netty4TcpChannel.java:72) ~[?:?] at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:511) ~[?:?] at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:504) ~[?:?] at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:483) ~[?:?] at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:424) ~[?:?] at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:121) ~[?:?] at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(AbstractNioChannel.java:327) ~[?:?] at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:343) ~[?:?] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:644) ~[?:?] at io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:556) ~[?:?] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:510) ~[?:?] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:470) ~[?:?] at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:909) ~[?:?] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_262] Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: sas3.onrc.ro/172.16.18.42:9300 at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:?] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:714) ~[?:?] at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:327) ~[?:?] at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340) ~[?:?] ... 6 more Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:?] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:714) ~[?:?] at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:327) ~[?:?] at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340) ~[?:?] ... 6 more [2025-09-17T14:13:06,646][INFO ][o.e.n.Node ] [yDJPxQE] stopping ... [2025-09-17T14:13:06,659][INFO ][c.f.s.a.s.SinkProvider ] [yDJPxQE] Closing DebugSink [2025-09-17T14:13:06,822][WARN ][o.e.d.z.ZenDiscovery ] [yDJPxQE] not enough master nodes discovered during pinging (found [[Candidate{node={yDJPxQE}{yDJPxQEqTC6XJfikTZgIZA}{IvifT4ShT3Gc3DQRsqXRDg}{sas1.onrc.ro}{172.16.18.44:9300}, clusterStateVersion=13187}]], but needed [2]), pinging again [2025-09-17T14:13:06,948][INFO ][o.e.n.Node ] [yDJPxQE] stopped     Could it be a connection error(ports blocked etc) or do I have to restart some services? ... View more

Sas studio error

by Calcite | Level 5 in Administration and Deployment
‎09-08-2025 03:41 AM
‎09-08-2025 03:41 AM
Hello, from time to time I get the following error after login: There was an error while starting SAS Studio Unable to create compute server session. No qualified launcher servers are available to complete request. Other than restarting SAS what can I do to solve this issue? ... View more

Re: SASUSER profile damaged

by Calcite | Level 5 in SAS Procedures
‎06-24-2025 07:31 AM
‎06-24-2025 07:31 AM
I have the same problem.   I found the sasmacr.sas7bcat file in /opt/sas/spre/home/SASFoundation/cmacros(linux) in 6 folders: or, hpf, dmine, modelsvr, decisionsvr and base. Which one should i rename,delete? After that a SAS restart is necessary? ... View more
Contact Me
Online Status
Offline
Date Last Visited
Monday
Quick links