Page MenuHomeVyOS Platform
Create Task
Maniphest T730

Configuration path: ... is not valid
Closed, InvalidPublicBUG
Actions

Description

Update: Re-opening, seems a broader issue. Any ideas what it could be / cause?

Hello,

New 1.2.0 user here. I assume the below error is a bug?

Best regards

vyos@vyos# set system host‐name

  Configuration path: system [host‐name] is not valid

Update: I was now able to set a new host-name. When I logged in from a different machine it miraculously worked and the error message disappeared. Still assuming there is something wrong here, somewhere?

Details

Difficulty level
Unknown (require assessment)
Version
1.2.0-rolling+201807040338
Why the issue appeared?
Will be filled on close

Event Timeline

binaryanomaly created this task.Jul 4 2018, 9:05 AM
binaryanomaly updated the task description. (Show Details)Jul 4 2018, 10:47 AM
c-po added a subscriber: c-po.Jul 4 2018, 11:11 AM
cpo@LR1:~$ configure
[edit]
cpo@LR1# set system host-name foo
[edit]
cpo@LR1# run show version
Version:          VyOS 1.2.0-rolling+201807022212
cpo@LR1# show system host-name
>host-name foo
[edit]
cpo@LR1# commit
[edit]

Works like a charm, at least with the version two days ago.

binaryanomaly added a comment.Jul 4 2018, 11:26 AM

Update: I was now able to set a new host-name. When I logged in from a different machine it miraculously worked and the error message disappeared. Still assuming there is something wrong here, somewhere?

Worked here now as well. Not sure what the problem was/is - this was a fresh install.

c-po closed this task as Invalid.Jul 4 2018, 1:29 PM

Please re-open if issue should occur again

binaryanomaly added a comment.Jul 4 2018, 3:51 PM

Couldn't reproduce on a fresh VM so this must have been a singular anomaly ;)

binaryanomaly renamed this task from Configuration path: system [host‐name] is not valid to Configuration path: ... is not valid.EditedJul 4 2018, 4:27 PM
binaryanomaly updated the task description. (Show Details)

Just had it here

vyos@er01# set system domain‐name localdomain

  Configuration path: system [domain‐name] is not valid
  Set failed

Retried a few times and then it worked. What could that be?

vyos@er01# set system domain-name localdomain
[edit]
binaryanomaly reopened this task as Open.Jul 4 2018, 4:33 PM
binaryanomaly added a comment.Jul 4 2018, 7:29 PM

May these entries in /var/log/vyatta/vyatta-commit.log be related?

[ interfaces ethernet eth0 duplex auto ]
Cannot set new settings: Invalid argument
  not setting autoneg

[ interfaces ethernet eth1 duplex auto ]
Cannot set new settings: Invalid argument
  not setting autoneg
c-po added a comment.Jul 4 2018, 7:46 PM

My guess it that something is wrong with your terminal or you have some weird unprintable characters in it.

What hardware/virtualizer are you running on?

binaryanomaly added a comment.Jul 4 2018, 7:50 PM

The host is Debian9 with KVM. I have a few VMs running there, never had a comparable issue.

I connect either from a Laptop with Debian9 or my Macbook Pro with iTerm via SSH.

binaryanomaly added a comment.Jul 5 2018, 7:46 AM

I just observed that I had these famous "kernel:[ ] Uhhuh. NMI received for unknown reason xx on CPU y." messages on the VM. Seems to be a common problem with the Q35 chipset in KVM. I suspect that this may have also caused the erratic behavior in VyOS. I'm now back on i440 and will close the bug until it occurs again.

binaryanomaly closed this task as Invalid.Jul 5 2018, 7:47 AM
syncer edited projects, added Invalid; removed VyOS 1.2 Crux.Oct 15 2018, 5:42 AM