SOLVED parse error: Expected value before ',' at line 48, column 4

  • Moderator

    FOG Version: 1.5.3 Master branch
    OS Version: Centos 7

    Getting this parse error when using quick deploy (other deploy types not tested). Deployment seems to continue just fine, though.

    0_1527842009991_IMG_20180601_102324.jpg


  • I should add there was a fix for this issue put in last night. Would you mind rerunning the installer and seeing if the issue is still present?


  • Reading through some of the forums, I saw the post about updating fog. I updated from 1.5.3 to 1.5.4 and that seems to have resolved the issue.

    Thanks


  • I too am getting this error, but at line 52 column 4.

    I get this when I am trying to do a full inventory on a new machine. It will continue and gives me a done at the end of inventory, but after rebooting it will tell me it is still not registered.

    I have attempted to register it a few times, and even with a done at the end never seems to register. I also do not see any entries for the workstation in fog management.

    I am running version 1.5.3

    It seems to be just this one workstation as the other workstations in the lab are working properly.

    As a side note, these workstations only have one nic in regards to your previous post.

    Thanks


  • @quazz I suspect the only time you’ll see the issue is when there’s multiple nics on the machine.

  • Moderator

    @tom-elliott Oddly enough, I ran another deploy on a different machine (same image) and it didn’t display this. Will rerun installer now anyway.


  • @quazz Just rerun the installer. When I pushed out the 1.5.3 update, I missed an argument in my script. That argument forces it to download the releases binaries file. That argument didn’t get set, so it will download the latest inits and kernels every install. No need for updates or anything in the branch tree.

  • Moderator

    @tom-elliott It says I’m already up to date. I’ve checked the working and dev-branch as well but can’t see any commits for last night?


  • I should add there was a fix for this issue put in last night. Would you mind rerunning the installer and seeing if the issue is still present?


  • This is okay I think. Annoying sure but as long as everything appears to be working properly it should be fine.

286
Online

9.1k
Users

15.7k
Topics

145.8k
Posts