KDE: NTP Configuration

Hi,
I've got NTP configured according to wiki.
My /etc/ntp.conf:
# With the default settings below, ntpd will only synchronize your clock.
# For details, see:
# - the ntp.conf man page
# - http://support.ntp.org/bin/view/Support/GettingStarted
# - https://wiki.archlinux.org/index.php/Ne … col_daemon
# Associate to public NTP pool servers; see http://www.pool.ntp.org/
server 0.europe.pool.ntp.org
server 1.europe.pool.ntp.org
server 2.europe.pool.ntp.org
server 3.europe.pool.ntp.org
# Only allow read-only access from localhost
restrict default noquery nopeer
restrict 127.0.0.1
restrict ::1
# Location of drift and log files
driftfile /var/lib/ntp/ntp.drift
logfile /var/log/ntp.log
# NOTE: If you run dhcpcd and have lines like 'restrict' and 'fudge' appearing
# here, be sure to add '-Y -N' to the dhcpcd_ethX variables in /etc/conf.d/net
It apparently works:
$ ntpq -np
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
5.9.85.232      195.58.160.5     3 u   46   64    1   47.672   -1.318   0.000
213.186.55.204  192.93.2.20      2 u   47   64    1   41.993   -0.320   0.000
194.177.210.54  .GPS.            1 u   48   64    1   98.900    0.403   0.000
62.116.130.3    192.53.103.108   2 u   48   64    1   50.181    8.957   0.000
$ date
Thu Oct 25 11:36:24 MSK 2012
$
I can't convince KDE Configure Date and Time Settings to take the setting, though. Before I started the NTP service the Set date and time automatically checkbox used to be grayed out, which makes sense. It recognizes my time zone (Europe/Moscow (MMT)), but I can't apply the settings:
Unable to connect to time server: europe.pool.ntp.org
Where is the catch? KDE taskbar clock keeps on showing, say, 07:36 AM UTC; even the Adjust Date and Time... dialog itself shows the right time!
Last edited by Llama (2012-10-25 07:58:43)

Which version of KDE are you running? I have got ntpd up and running und I do not have any problems with kde time settings. In fact, iirc, I had to fire up ntpd to make it work (but I'm not sure, has been some time). Greying out can also mean that there some rights issues... have you tried running systemsettings with sudo?
Oh btw: if time and date shows the correct time, but clock doesn't, it's often because the clock isn't updated instantaneously. Wait a bit or remove and add the clock again

Similar Messages

  • Use of NTP pool in NTP configuration

    I had the following queries with respect to the use of NTP pool in the NTP configuration on RHEL:
    1) I see the following public servers  from the pool.ntp.org project in the default /etc/ntp.conf file.
    server  0.rhel.pool.ntp.org
    server 1.rhel.pool.ntp.org
    Would using these servers be fine or are there servers specific to India as we are located in India?
    2) Time to be taken from the public servers above may not be ideal, I was wondering how much could the difference in time be say over a 1 month period?
    I hope, my question is clear.
    Please revert with the reply to my query.
    Regards

    1) I see the following public servers  from the pool.ntp.org project in the default /etc/ntp.conf file.
    server  0.rhel.pool.ntp.org
    server 1.rhel.pool.ntp.org
    Would using these servers be fine or are there servers specific to India as we are located in India?
    Use the <n>.in.pool.org servers because they are much closer to you.
    2) Time to be taken from the public servers above may not be ideal, I was wondering how much could the difference in time be say over a 1 month period?
    How long is a piece of string?  Your question is unanswerable.  Syncing with external clock references is fine because you can use as many reference clocks as it takes you to feel comfortable; I'd suggest 4 or 5, and also turn on the local software reference clock.
    111111112dsfsdfsdfsdfsdf

  • KDE: fonts configuration files

    Hi,
    Where are KDE fonts configurations located? Fonts, antialiasing, etc., user and root.

    The KDE font settings (and some other settings like colors) are located in:
    ~/.kde4/share/config/kdeglobals

  • NTP Configuration on IDS4215

    Hi,
    I am new to the IDS environment, we are planing to configure a NTP server on the IDS 4215 box.
    I have a completed command set for the same as mentioned below.
    sensor# configure terminal
    sensor(config)# service host
    sensor(config-hos)# ntp-option enable
    sensor(config-hos-ena)# ntp-servers ip_address key-id key_ID
    now the problem for me is i don't have the Key-id & Key-value for my ntp server.
    Can some one help me configue NTP with out the key-id information.

    Unfortunately 5.1(8)E3 is pretty old and doesn't support unauthenticated ntp.
    The 5.1 train has been End Of Saled, and is quickly approaching End Of Life/ End Of Signature Support:
    http://www.cisco.com/en/US/prod/collateral/vpndevc/ps5729/ps5713/ps2113/end_of_life_notice_c51-468830.html
    Last date for Signatures for the 5.1 version is Oct 24th of this year.
    So you only have around 4 months left before you would be forced to upgrade to 6.0 in order to continue getting signature updates.
    The 4215 is also End Of Saled, but it's End Of Signature Support is not until July 29th 2011.
    http://www.cisco.com/en/US/prod/collateral/vpndevc/ps5729/ps5713/ps4077/ps5367/end_of_life_notice_for_cisco_ids_4215_sensor.html
    Version 6.0 is the last version to support the IDS-4215, so Signature Updates for 6.0 for the IDS-4215 will continue until at least July 29th 2011.
    So if you upgrade to 6.0 now, you will still have 2 more years of signature updates before you need to purchase a new sensor.
    The 6.0(5)E3 version does support the unauthenticated ntp option.
    So you will want to plan an upgrade to 6.0 sometime in the next 4 months.
    In the meantime you will need to use key authenticated ntp.
    If you have access to a router you could try using the router as a temporary inbetween server.
    The router would be configured to get its time for your existing ntp server. Talk to your network administrator on how to set this up.
    Then configure the router to also be an ntp server with an authenitcated key.
    Here is a section of the CLI Guide explaining how to setup the router as a key authenticated ntp server:
    http://www.cisco.com/en/US/docs/security/ips/7.0/configuration/guide/cli/cli_setup.html#wp1035649
    The sensor would be configured to use the router as the ntp server using that key.
    This would be a temporary workaround until you can get upgraded to 6.0.

  • NTP Configuration -- Help

    Hi,
    I have had some difficulty configuring the NTP protocol based on my timezone.
    Here is my problem:
    Eastern Daylight Time (EDT) which is 5 hours off from the UTC.
    After the time change in October, timezone becomes Eastern Standard time which 4 hours off the UTC.
    Now when I configure NTP my time is always one hour ahead like it is EST when we still are in EDT.
    Can somebody explain how to make this happens, if possible?
    Also, can somebody recommend some NTP servers?
    I appreciate your help.

    That is strange, but is the date correct on your router - that is, is it a summertime date.
    But there is something funny about your timezones. You seem to have you summer timezone as UTC-5 and your winter as UTC-4. I would have expected it the other way round: EST=UTC-5, EDT=UTC-4. Clocks go forward an hour in summer, not back.
    Kevin Dorrell
    Luxembourg

  • NTP configurations for IDS

    Hi all,
    I'm trying to configure all IDS systems to use NTP service, but the software (IDM as well as VMS) asks for NTP server IP, Key and Key ID. All these fields seem to be mandatory. My NTP server is not configured for authentication. What can I do? Is there a way to configure IDS in order to interface with a such NTP server?
    Thanks,
    Chiara

    How to use Linux/Unix as an authenticated server.
    Currently Cisco IDS/IPS sensors do not support unauthenticated NTP. That feature has been requested under CSCeg35205, but is not scheduled for any software release at this time.
    One way to get around this problem is to configure a router or a Linux host to act as an NTP server with authentication. That host can either act as a stand-alone server, or it can be configured to synchronize its clock to another NTP server without authentication. This allows it to act as a sort of shim between a router that does not allow authentication and a sensor that requires authentication.
    Officially, Cisco IDS sensors support compatibility with only Cisco routers as the ntp server. However I have successfully used a Red Hat Linux box as the server with no problems. I've attached sample configuration files for Linux, but they should work with other flavors of *nix operating systems.
    Just copy the attached file "ntp.conf" to the /etc/ directory and copy the file "keys" to the /etc/ntp/ directory (be sure to back up any existing files). Then edit those config files for your specific network as described in the comments. Then start (or restart) ntp. This is usually done by executing (as root) the startup script, such as "/etc/init.d/ntpd start" or "/etc/init.d/ntpd restart". Wait about 20 minutes before trying to set up a sensor to use the new server, because it takes a while for it to stabilize before it will accept any connections.
    I'll watch this thread for a while and will try to help with any troubles you may have.

  • NTP configuration

    Hi all,
    I have some routers and a lot of switches that I configured the time and date manually. Now I have configured an NTP Server and want to configure all my routers and switches to synchronize to this NTP Server.
    The question is: should I remove the time, date, zone, clock summer-time reccuring, etc., that was configured manually?
    I think the best idea is to remove all time settings that was set mannualy, before configuring the router for NTP server.

    Time zone and summer/winter time can still be put to use. It depends whether the ntp server is using the same timezone as your network. If not, the local settings can be used to calculate the correct offset.
    Example: ntp server sends time in GMT. Nodes are in timezone GMT+1 and use the summertime. You will need to configure this on your nodes.
    The time itself will be overruled automatically by the ntp-update if the diff is small enough. A reboot may be required otherwise.
    Regards,
    Leo

  • Oracle VM Server 2.2 Linux Guest cannot ntp to server properly

    Hi All,
    I have installed a VM guest Oracle Linux Enterprise 5U6 in Oracle VM server 2.2. I follow below procedure to config NTP in VM server.
    https://blogs.oracle.com/virtualization/entry/configuring_ntp_services_for_oracle
    However, when I apply the NTP configuration with VM server itself on the Guest, it detects the NTP server in high jitter value. Even though the stratrum is lower than the local host, It still cannot use that server as NTP source. Here is some information about the NTP debug and IP address.
    IP Address:
    Oracle VM Server: 172.16.8.100
    VM Guest: 172.16.8.102
    Debug on VM Guest:
    # ntpdate -d 172.16.8.100
    26 Mar 13:54:18 ntpdate[697]: ntpdate [email protected] Tue Dec 8 20:30:45 UTC 2009 (1)
    Looking for host 172.16.8.100 and service ntp
    host found : 172.16.8.100
    transmit(172.16.8.100)
    receive(172.16.8.100)
    transmit(172.16.8.100)
    receive(172.16.8.100)
    transmit(172.16.8.100)
    receive(172.16.8.100)
    transmit(172.16.8.100)
    receive(172.16.8.100)
    transmit(172.16.8.100)
    server 172.16.8.100, port 123
    stratum 3, precision -20, leap 00, trust 000
    refid [172.16.8.100], delay 0.02585, dispersion 0.00037
    transmitted 4, in filter 4
    reference time: d31a8fd0.c06d7d27 Mon, Mar 26 2012 13:48:48.751
    originate timestamp: d31a9168.774cbbe0 Mon, Mar 26 2012 13:55:36.466
    transmit timestamp: d31a911b.138bdec5 Mon, Mar 26 2012 13:54:19.076
    filter delay: 0.02725 0.02614 0.02585 0.02626
    0.00000 0.00000 0.00000 0.00000
    filter offset: 77.38879 77.38864 77.38926 77.38931
    0.000000 0.000000 0.000000 0.000000
    delay 0.02585, dispersion 0.00037
    offset 77.389261
    26 Mar 13:54:19 ntpdate[697]: step time server 172.16.8.100 offset 77.389261 sec
    High jitter to the server but actualyl they are on the single box
    # ntpq -p
    remote refid st t when poll reach delay offset jitter
    ==============================================================================
    172.16.8.100 172.16.90.1 3 u 47 64 3 0.265 2704.42 2488.59
    LOCAL(0) .LOCL. 10 l 44 64 3 0.000 0.000 0.004
    Thanks.
    Rgds,
    Jacky

    Hi Avi,
    Thanks for your reply. Due to we do not have Oracle VM Manager, I did configure the VM guest to point the internal NTP server (172.16.90.1) which is mapped by Oracle VM server, but the high jitter is still existed while the guest can ntpq the NTP server. Thanks.
    Oracle VM Server
    #ntpstat
    synchronised to NTP server (172.16.90.1) at stratum 3
    time correct to within 56 ms
    polling server every 1024 s
    #ntpq -p
    remote refid st t when poll reach delay offset jitter
    ==============================================================================
    *172.16.90.1 10.1.22.230 2 u 551 1024 377 0.355 0.292 0.065
    172.16.190.1 .INIT. 16 u - 1024 0 0.000 0.000 0.000
    LOCAL(0) .LOCL. 10 l 46 64 377 0.000 0.000 0.001
    VM Guest Oracle Linux
    # ntpq -p
    remote refid st t when poll reach delay offset jitter
    ==============================================================================
    172.16.90.1 10.1.22.230 2 u 61 64 3 0.432 252.261 3169.53
    172.16.190.1 .INIT. 16 u - 64 0 0.000 0.000 0.000
    LOCAL(0) .LOCL. 10 l 34 64 7 0.000 0.000 0.008
    # ntpstat
    synchronised to local net at stratum 11
    time correct to within 448 ms
    polling server every 64 s
    # ntpdate -d 172.16.90.1
    26 Mar 15:47:15 ntpdate[27478]: ntpdate [email protected] Tue Dec 8 20:30:45 UTC 2009 (1)
    Looking for host 172.16.90.1 and service ntp
    host found : 172.16.90.1
    transmit(172.16.90.1)
    receive(172.16.90.1)
    transmit(172.16.90.1)
    receive(172.16.90.1)
    transmit(172.16.90.1)
    receive(172.16.90.1)
    transmit(172.16.90.1)
    receive(172.16.90.1)
    transmit(172.16.90.1)
    server 172.16.90.1, port 123
    stratum 2, precision -20, leap 00, trust 000
    refid [172.16.90.1], delay 0.02594, dispersion 0.00052
    transmitted 4, in filter 4
    reference time: d31aa515.a637fc1e Mon, Mar 26 2012 15:19:33.649
    originate timestamp: d31aabaf.06173915 Mon, Mar 26 2012 15:47:43.023
    transmit timestamp: d31aaba2.61117b52 Mon, Mar 26 2012 15:47:30.379
    filter delay: 0.02631 0.02605 0.02594 0.02594
    0.00000 0.00000 0.00000 0.00000
    filter offset: 12.64269 12.64337 12.64397 12.64443
    0.000000 0.000000 0.000000 0.000000
    delay 0.02594, dispersion 0.00052
    offset 12.643971
    26 Mar 15:47:30 ntpdate[27478]: step time server 172.16.90.1 offset 12.643971 sec
    Rgds,
    Jacky

  • ISE 1.1.2 patch 8 NTP Service failing

    Hi all,
    after a recent upgrade of my ISE deployment from 1.1.1 patch 3 to 1.1.2 patch 8, the NTP service on the ISE now crashes at regular intervals.
    Can I have some help debugging this issue? I would like to check the logs but there are so many that I am not sure which one to turn debugging on.
    Also, just wanted to know if anyone has seen this issue before or knows if this is a known issue when runing 1.1.2 patch 8.
    Thanks everyone!
    Mario                  

    You cannot install a patch whose  version is lower than the patch that is currently installed on ISE.  Similarly, you cannot roll back changes of a lower version patch if a  higher version is currently installed on Cisco ISE.
    For NTP Configuration, you please  check the below link
    http://www.cisco.com/en/US/docs/security/ise/1.1/cli_ref_guide/ise_cli_app_a.html#wp2267226
    http://www.cisco.com/en/US/docs/security/ise/1.1.1/upgrade_guide/upgrade.html

  • Do I need to open ports for NTP?

    I just noticed that my hwclock was off by nearly 30 seconds. It's almost certainly due to the recent initscripts update.
    As I was looking into resetting the clock, I found out that openntpd is deprecated so I've switched to ntp, configured the daemon, reset the time with ntpd -q, and started the daemon. The time is not accurate again.
    I remember back when I first installed Arch I tried to set up ntp but it didn't seem to work, so I tried openntpd and stuck with that. I reached the conclusion that ntp required open ports, which I felt was unnecessary given that openntpd could do the same thing without open ports.
    Now that I'm looking at it again, I can't find any definitive answer...
    Do I need to open ports for ntp if I only want to sync the system that it's running on?

    ISC ntpd (the ntp package) will open UDP 123 on all your interfaces regardless of what you do with it. It will work anyway even if you block this port in iptables, assuming that you're allowing responses to established traffic as usual - your outbound mobilization requests to your chosen servers will be enough to allow the responses, and the same with further traffic sent for the lifetime of ntpd. Using iptables like this is probably the easiest way to secure ntpd.
    There's also some defense in depth you can do:
    - run ntpd as non-root
    - run it chrooted to some safe directory (really only makes sense when doing non-root as well, since root can break out of a chroot)
    - apply ntpd's built-in access controls (see examples in ntpd.conf, and full docs in ntp_acc(5))
    I accomplish the first two of these by chowning /var/lib/ntp (and any contents) to ntp:ntp (so ntpd can write ntp.drift there when non-root), by using a driftfile path relative to the chroot in ntp.conf, and by setting NTPD_ARGS="-g -i /var/lib/ntp -u ntp:ntp" in /etc/conf.d/ntp-client.conf.
    For the third, I chose to not allow any remote traffic to initiate anything with my ntpd, with this /etc/ntp.conf:
    server ac-ntp0.net.cmu.edu iburst
    server ac-ntp1.net.cmu.edu iburst
    server ac-ntp2.net.cmu.edu iburst
    server ac-ntp3.net.cmu.edu iburst
    server ac-ntp4.net.cmu.edu iburst
    restrict default nomodify nopeer noquery
    restrict 127.0.0.1
    driftfile /ntp.drift
    Note the two "restrict" lines. The first shuts out remote access of most kinds, and the second allows the local machine all the access that would also be denied to it as well otherwise by the first rule. Note also the driftfile path, relative to the chroot of /var/lib/ntp/.
    With all these security features, ISC ntpd can be just as safe as openntpd.
    The use of the "iburst" keyword on the server lines to recover more quickly from out-of-contact conditions is also quite nice, and not rude to the remotes like "burst" would be.
    One of the nicest other features of ISC ntpd is that it's smart enough to notice when network state changes occur, like bringing a VPN up/down, changing routes, or switching from wired to wireless and back. openntpd tended to just lose connections in these cases.

  • KDE SC 4.4.0 released

    KDE announced the availability of its Software Compilation 4.4, "Caikaku".
    You will find all upstream changes and new features on their website. As usual we provide
    the latest packages for Arch.
    Unfortunately this update will need some user intervention due to a pacman
    limitation. Therefore you have to update in two steps:
    % pacman -Sy --asdeps qt
    % pacman -Su
    Be aware of the following problems that might occur:
    * The usage of bitmap fonts like terminus will be broken when using the
    proprietary nvidia driver.
    * If you update from virtuoso 5 as nepomuk backend as it was provided in
    the kde-unstable or testing repository you will have to convert
    your database or simply remove
    ~/.kde4/share/apps/nepomuk/repository/main/data/virtuosobackend. The latter
    is of course only recommend if you had not used nepumuk's tagging and
    comment features.
    * In case of any error, try using a new user account or (re)moving KDE's
    configuration which can be found at ~/.kde4 /tmp/kde-* /var/tmp/kdecache-*.
    Akonadi saves its data at ~/.config/akonadi and ~/.local/share/akonadi

    I let my nieces and nephews use my Internet connection while I was on holidays and now I am capped and I am only half way through my month.  So I am still updating painfully slowly   Will be updating my plan for the month in the morning.
    However I was able to download the packages from ftp.archlinux.org (extra), I don't normally use this mirror but I will be updating the rest of my machines manually while I have the day off.
    Edit:
    toad wrote:Cheers, Allan. Then again, who knows? Perhaps he is the wizard of Oz? I've heard they're ahead of our time down there... (okay, ban me for bad jokes).
    Okay this made me laugh!
    Last edited by Tyriel (2010-02-09 11:26:41)

  • NTP reverts to local 127.127.1.0 (VMware)

    HI. I am experiencing an issue with a LAB deployment of CISCO ISE. I cannot get the NTP to sync and the DB services to start. See output below. Any help will be appreciated
    iselab/admin# sh ntp
    Configured NTP Servers:
    172.16.0.101
    synchronised to local net at stratum 11
    time correct to within 11 ms
    polling server every 1024 s
    remote refid st t when poll reach delay offset jitter
    ==============================================================================
    *127.127.1.0 .LOCL. 10 l 26 64 377 0.000 0.000 0.001
    172.16.0.101 172.16.0.253 2 u 1630 1024 0 0.000 0.000 0.000
    * Current time source, + Candidate
    Warning: Output results may conflict during periods of changing synchronization.

    The clock sync can take up to 20 minutes to complete.  You may also want to ensure that the ESXi server is also using the same NTP server as your ISE VM.  Since 127.127.1.0 is the local clock, having the ESXi configured this way will help to ensure the correct time in your VM.
    The following quote is taken from the page linked below it:
    "For example, NTP uses a pseudo IP address 127.127.8.n to access a Meinberg radio clock installed at the local computer. To access its own system clock, also called the local clock , NTP uses the pseudo IP address 127.127.1.0. This IP address must not be mixed up with 127.0.0.1, which is the IP of the localhost, i.e. the computer's loopback interface."
    http://www.meinbergglobal.com/english/info/ntp.htm
    Please let me know if this fixes your issue.  If it does, please rate this answer and mark your question as Answered.
    Charles Moreton

  • PRVF-5408 : NTP Time Server is common only to the following node

    Hi all,
    i found the following errors in $GRID_HOME/log/`hostname`/alert`hostname`.log :
    2011-12-21 01:24:26.854
    [client(18213)]CRS-10051:CVU found following errors with Clusterware setup : PRVF-5408 : NTP Time Server "193.204.114.233" is common only to the following nodes "e1dbp01na"
    PRVF-5408 : NTP Time Server "193.204.114.232" is common only to the following nodes "e1dbp01nb"
    2011-12-27 13:25:49.410
    [client(20522)]CRS-10051:CVU found following errors with Clusterware setup : PRVF-5408 : NTP Time Server "193.204.114.233" is common only to the following nodes "e1dbp01na"
    2011-12-29 01:26:10.541
    [client(18799)]CRS-10051:CVU found following errors with Clusterware setup : PRVF-5408 : NTP Time Server "193.204.114.232" is common only to the following nodes "e1dbp01na"
    The weird thing is that ntp configuration is symmetrical between both nodes and the ntp server "193.204.114.232" does not appear in /etc/ntp.conf
    Why ntpd should use a server which is not listed in /etc/ntpd.conf ?
    thanks,
    Andrea

    Yes, that IP is a valid hostname: 193.204.114.232 is ntp1.inrim.it, the "official" italian ntp server.
    193.204.114.232 and ntp1.inrim.it do not appear in /etc/hosts, /etc/resolve.conf Ntp configuration is :
    [oracle@e1dbp01na ~]$ cat /etc/sysconfig/ntpd
    # Drop root to id 'ntp:ntp' by default.
    OPTIONS="-x -u ntp:ntp -p /var/run/ntpd.pid"
    # Set to 'yes' to sync hw clock after successful ntpdate
    SYNC_HWCLOCK=no
    # Additional options for ntpdate
    NTPDATE_OPTIONS=""
    [oracle@e1dbp01na ~]$ grep ^server /etc/ntp.conf
    server 127.127.1.0
    server 172.18.1.7
    server 172.18.1.70
    and cluvfy comp clocjsync shows:
    NTP common Time Server Check started...
    NTP Time Server "193.204.114.232" is common to all nodes on which the NTP daemon is running
    NTP Time Server ".INIT." is common to all nodes on which the NTP daemon is running
    NTP Time Server ".LOCL." is common to all nodes on which the NTP daemon is running
    Check of common NTP Time Server passed
    ...

  • NTP(Network Time Protocol) Error whil installing Oracle 11gR2 RAC

    Dear Friends,
    I have installed oracle 11gr2 clusterware software in two node RAC. While i run the CLUVFY.SH, It shows error in NTP configuration.
    1)I add "-x" parameter in "/etc/sysconfig/ntp" configuration file. and start the ntpd service and run the cluvfy.sh . then i got the below error.
    Check: CTSS state
    Node Name State
    rac2 Observer
    rac1 Observer
    CTSS is in Observer state. Switching over to clock synchronization checks using NTP
    Starting Clock synchronization checks using Network Time Protocol(NTP)...
    NTP Configuration file check started...
    The NTP configuration file "/etc/ntp.conf" is available on all nodes
    NTP Configuration file check passed
    Checking daemon liveness...
    Check: Liveness for "ntpd"
    Node Name Running?
    rac2 no
    rac1 no
    Result: Liveness check failed for "ntpd"
    PRVF-5415 : Check to see if NTP daemon is running failed
    Result: Clock synchronization check using Network Time Protocol(NTP) failed
    PRVF-9652 : Cluster Time Synchronization Services check failed
    Post-check for cluster services setup was unsuccessful on all the nodes.
    =============================================================================================
    2)Down the ntpd service in both nodes and run the CLUVFY.SH.
    Check: CTSS state
    Node Name State
    rac2 Observer
    rac1 Observer
    CTSS is in Observer state. Switching over to clock synchronization checks using NTP
    Starting Clock synchronization checks using Network Time Protocol(NTP)...
    NTP Configuration file check started...
    The NTP configuration file "/etc/ntp.conf" is available on all nodes
    NTP Configuration file check passed
    Checking daemon liveness...
    Check: Liveness for "ntpd"
    Node Name Running?
    rac2 no
    rac1 yes
    Result: Liveness check failed for "ntpd"
    PRVF-5415 : Check to see if NTP daemon is running failed
    Result: Clock synchronization check using Network Time Protocol(NTP) failed
    PRVF-9652 : Cluster Time Synchronization Services check failed
    Post-check for cluster services setup was unsuccessful on all the nodes.
    ==========================================================================
    3)Based on some website advice, I down the ntpd service and move the "/etc/ntpd.conf" to another location.Then i got the below error.
    Result: Query of CTSS for time offset passed
    Check CTSS state started...
    Check: CTSS state
    Node Name State
    rac2 Observer
    CTSS is in Observer state. Switching over to clock synchronization checks using NTP
    Starting Clock synchronization checks using Network Time Protocol(NTP)...
    NTP Configuration file check started...
    ERROR:
    PRVF-5402 : Warning: Could not find NTP configuration file "/etc/ntp.conf" on node "rac2"
    PRVF-5405 : The NTP configuration file "/etc/ntp.conf" does not exist on all nodes
    rac2
    PRVF-5414 : Check of NTP Config file failed on all nodes. Cannot proceed further for the NTP tests
    Result: Clock synchronization check using Network Time Protocol(NTP) failed
    PRVF-9652 : Cluster Time Synchronization Services check failed
    =============================================================
    What should i do to solve this issue?? Please help me ...

    Hi,
    I start the ntpd start the service in both node and done the CLUVFY.SH.
    The output is below,
    Checking if CTSS Resource is running on all nodes...
    Check: CTSS Resource running on all nodes
    Node Name Status
    rac2 passed
    rac1 passed
    Result: CTSS resource check passed
    Querying CTSS for time offset on all nodes...
    Result: Query of CTSS for time offset passed
    Check CTSS state started...
    Check: CTSS state
    Node Name State
    rac2 Observer
    rac1 Observer
    CTSS is in Observer state. Switching over to clock synchronization checks using NTP
    Starting Clock synchronization checks using Network Time Protocol(NTP)...
    NTP Configuration file check started...
    The NTP configuration file "/etc/ntp.conf" is available on all nodes
    NTP Configuration file check passed
    Checking daemon liveness...
    Check: Liveness for "ntpd"
    Node Name Running?
    rac2 yes
    rac1 yes
    Result: Liveness check passed for "ntpd"
    Checking NTP daemon command line for slewing option "-x"
    Check: NTP daemon command line
    Node Name Slewing Option Set?
    rac2 yes
    rac1 yes
    Result:
    NTP daemon slewing option check passed
    Checking NTP daemon's boot time configuration, in file "/etc/sysconfig/ntpd", for slewing option "-x"
    Check: NTP daemon's boot time configuration
    Node Name Slewing Option Set?
    rac2 yes
    rac1 yes
    Result:
    NTP daemon's boot time configuration check for slewing option passed
    NTP common Time Server Check started...
    PRVF-5410 : Check of common NTP Time Server failed
    PRVF-5416 : Query of NTP daemon failed on all nodes
    Result: Clock synchronization check using Network Time Protocol(NTP) passed
    Oracle Cluster Time Synchronization Services check passed
    ========================================================================================
    [oracle@rac1 ~]$ /u01/app/grid/oracle/product/10.2.0/db_1/bin/cluvfy comp clocksync
    Verifying Clock Synchronization across the cluster nodes
    Checking if Clusterware is installed on all nodes...
    Check of Clusterware install passed
    Checking if CTSS Resource is running on all nodes...
    CTSS resource check passed
    Querying CTSS for time offset on all nodes...
    Query of CTSS for time offset passed
    Check CTSS state started...
    CTSS is in Observer state. Switching over to clock synchronization checks using NTP
    Starting Clock synchronization checks using Network Time Protocol(NTP)...
    NTP Configuration file check started...
    NTP Configuration file check passed
    Checking daemon liveness...
    Liveness check passed for "ntpd"
    NTP daemon slewing option check passed
    NTP daemon's boot time configuration check for slewing option passed
    NTP common Time Server Check started...
    PRVF-5410 : Check of common NTP Time Server failed
    PRVF-5416 : Query of NTP daemon failed on all nodes
    Clock synchronization check using Network Time Protocol(NTP) passed
    Oracle Cluster Time Synchronization Services check passed
    Verification of Clock Synchronization across the cluster nodes was successful.
    [oracle@rac1 ~]$
    ================================================================================
    I hope the problem solved. Am i correct??

  • [KDE] sftp:// and smb:// are turtles

    I have had experiments wrt speed between self-made home NAS and my workstation (with NetGear router between them). If I use smbclient to connect samba on NAS or lftp to connect to SSH on NAS, all is OK: the speed is about 12MiB/s, and this is a limit for 100Mbit LAN. If I use Krusader, a speed drops down to 8-9MiB/s for samba, and to 3MiB/s (!) for SSH. CPU consumption is about zero.
    Is there those KDE secret configuration places to cure this KDE's shame?

    kokoko3k wrote:Yeah, vote for that, but vote for this too!
    https://bugs.kde.org/show_bug.cgi?id=178678
    ...which is valid for cifs mounted folders too
    Done
    BTW, I have tested throughputs for differemt use cases here: https://bbs.archlinux.org/viewtopic.php?id=115788

Maybe you are looking for