Jump to content
We're Hiring! Full Stack Developer ×
  • magical escape share


    aladdin134
    • Retest Minor
    Message added by limetech

    Please be aware that these comments were copied here from another source and that the date and time shown for each comment may not be accurate.

    I fat fingered a docker path setting up a route to a folder ("/mnt/user/[share name]\"), and now I have a "\" share. this breaks all sorts of things, and I get an error message hidden under the header of every page of my UI, which breaks a lot of functionality. I can't find a way to persistently remove the share in the .ini files in /var/local/emhttp/plugins folder, which is the only such files I can find. I've uninstalled all the dynamix plugins I had, so I don't even know why the template.php is rendering.


     

    Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in state/sec.ini on line 273 in /usr/local/emhttp/plugins/dynamix/template.php on line 25
    
    Warning: syntax error, unexpected $end, expecting ']' in state/shares.ini on line 137 in /usr/local/emhttp/plugins/dynamix/template.php on line 29
    
    Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in state/sec_nfs.ini on line 153 in /usr/local/emhttp/plugins/dynamix/template.php on line 30
    
    Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in state/sec_afp.ini on line 267 in /usr/local/emhttp/plugins/dynamix/template.php on line 31

     




    User Feedback

    Recommended Comments

    Not entirely clear what you mean by a \ share. Maybe if you could tell us exactly what path you fat-fingered it would clear things up.

     

    If you mean the host path was literally \ then that would go away with a reboot as long as the docker is gone and doesn't recreate it, since all the paths at that level are in RAM.

     

    If that isn't what you mean explain further.

    Link to comment

    And the templates won't go away simply by removing plugins since the dockerman "plugin" is builtin.

     

    Maybe getting us the diagnostics will tell us more. They don't often include much about specific dockers, but they might give us some idea about your actual User Shares.

     

    Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

    Link to comment

    I now have an entry in my /var/local/emhttp/shares.ini file that looks like 

    ["\"]                                                                                                                   
    name="\"                                                                                                                
    nameOrig="\"                                                                                                            
    comment=""                                                                                                              
    allocator="highwater"                                                                                                   
    splitLevel=""                                                                                                           
    floor="0"                                                                                                               
    include=""                                                                                                              
    exclude=""                                                                                                              
    useCache="no"                                                                                                           
    cow="auto"                                                                                                             
    color="yellow-on"                                                                                                      
    free="17603187952"                                                                                                      
    size="0"                                                                                                                
    luksStatus="0"       

     

    this has persisted through a reboot

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...