DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Server Upgrade and now Site History Log full

Sort:
You are not authorized to post a reply.





New Around Here





    GoDaddy upgraded their plesk servers and my canary in a coal mine site is having major problems. The site goes down with the this error message:

    System.Data.SqlClient.SqlException (0x80131904): Could not allocate space for object 'dbo.EventLog'.'PK_EventLogMaster' in database 'Database Name' because the 'PRIMARY' filegroup is full.

    My schedulehistory log has over 35000 items.

    I'm on DNN 8.04 with some Mandeeps Live extensions.

    I tried delete from eventlog

    I was able to get the site back up after that, and I found and installed the ScheduleHistory extension from IowaGurus. (Thanks for that!) I was able to run the items, but it didn't delete the schedulehistory log items.

    I went into the scheduler and changed everything to one week for pinging, etc. to try to buy some time.

    I went into the event viewer and got the following errors all with saying that access to that file is denied? But according to my permissions, everything has full read/write access to that directory and subdirectories?

    AbsoluteURL:

    DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

    ExceptionGUID:bf627dec-a6d0-4d44-9296-e795f7d41675

    AssemblyVersion:

    PortalId:-1

    UserId:-1

    TabId:-1

    RawUrl:

    Referrer:

    UserAgent:

    ExceptionHash:nClUreaxfbMenNWYa78Rcg==

    Message:Access to the path 'G:\PleskVhosts\onesexyscooter.com\httpdocs\App_Data\Search\segments_159r8' is denied.

    StackTrace:

       at Lucene.Net.Store.SimpleFSDirectory.OpenInput(String name, Int32 bufferSize)
       at Lucene.Net.Store.FSDirectory.OpenInput(String name)
       at Lucene.Net.Index.SegmentInfos.Read(Directory directory, String segmentFileName)
       at Lucene.Net.Index.SegmentInfos.AnonymousClassFindSegmentsFile.DoBody(String segmentFileName)
       at Lucene.Net.Index.SegmentInfos.FindSegmentsFile.Run(IndexCommit commit)
       at Lucene.Net.Index.SegmentInfos.Read(Directory directory)
       at Lucene.Net.Index.IndexWriter.Init(Directory d, Analyzer a, Boolean create, IndexDeletionPolicy deletionPolicy, Int32 maxFieldLength, IndexingChain indexingChain, IndexCommit commit)
       at Lucene.Net.Index.IndexWriter..ctor(Directory d, Analyzer a, MaxFieldLength mfl)
       at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.get_Writer()
       at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.Delete(Query query)
       at DotNetNuke.Services.Search.Internals.InternalSearchControllerImpl.DeleteSearchDocumentInternal(SearchDocument searchDocument, Boolean autoCommit)
       at DotNetNuke.Services.Search.Internals.InternalSearchControllerImpl.DeleteSearchDocument(SearchDocument searchDocument)
       at DotNetNuke.Services.Search.SearchEngine.DeleteRemovedObjects()
       at DotNetNuke.Services.Search.SearchEngineScheduler.DoWork()

     

    InnerMessage:

    InnerStackTrace:

    
     

     

    Source:Lucene.Net

    FileName:

    FileLineNumber:0

    FileColumnNumber:0

    Method:

    Server Name

     

    --------------------------------------

    I don't care about this site, but there are other sites that I work on that has vital information for the elderly in our communities. I'm afraid that this will happen to those sites when GoDaddy does their upgrade.

    Thanks for any help.






    New Around Here





      OK, I can't change permissions on that file and I can't download it. ( segments_159r8) If I delete it will the system rebuild it?





      New Around Here





        Found this from Sebastian (very helpful)

        Fixing DNN Site Search

        If no search are displayed just after you installed DNN, you don’t need to worry – the search indexer needs a couple of minutes to build up. But if this happens, after you added quite some content, there might be several reasons:

        • The search indexer is not running. Please enter Host > Scheduler and make sure, the index job is enabled and runs at least once per hour. Check the schedule history to verify it gets executes and finishes.
        • if you are missing content of a specific module type, the module might not support search. Go to Extensions in Host menu and click edit for the module definition. Check whether “is Searchable” is enabled.
        • the search index might have got corrupted by accident

        Rebuilding the Search Index

        If the search index got corrupted, you’ll have to delete and rebuild the search index tables manually.

        DNN 7.1.0 and later is using Lucene.Net search engine, which stores its index in file system. To clear the index, remove all files inside /app_data/search. This folder is not accessible via the DNN file manager, you need to connect using FTP, WebDAV or RDP to delete the files.

         

        ---------------------------------------------------------------------

        Now I just have to figure out how to delete the schedulehistory log?






        New Around Here





          OK, I did truncate table schedulehistory and even though this was 8.04 it seemed to work. I may be OK now. I'm watching... this thing has been so stable until they did the server upgrade.





          Veteran Member





            You seem to have 2 things in this topic.
            1. Host - Scheduled tasks - purge schedule history might help.
            And take a look at the timing of things. What I remember from those old versions that if a scheduled task fails and it will try again too quickly, it can get funky. Or if a job is still running and it tries again. Especially if you have so many records.
            If you worry about the file not being recreated, you can also truncate the table.
            https://support.managed.c...ms-sql-database.aspx

            2. Have you tried re-index? Admin - Search admin - re-index
            Tjep's digital agencyRegards,
            Tycho de Waard

            Tjep's digital agency
            We just love DNN
            https://www.tjeps.com





            Veteran Member





              No, your DNN 804 is not stable. In fact, it is very unsafe to use this version as it has several severe vulnerabilities that are being exploited in the wild and automatically. 9.9.2 is the minimum but 9.10 is better
              Tjep's digital agencyRegards,
              Tycho de Waard

              Tjep's digital agency
              We just love DNN
              https://www.tjeps.com





              Veteran Member





                I agree with Tycho you should upgrade to latest version to DNN 9.10.2 and remove Telerik components (see release notes for instrunctions)
                You are not authorized to post a reply.

                These Forums are dedicated to the discussion of DNN Platform.

                For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

                1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
                2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
                3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
                4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
                5. No Flaming or Trolling.
                6. No Profanity, Racism, or Prejudice.
                7. Site Moderators have the final word on approving / removing a thread or post or comment.
                8. English language posting only, please.

                Would you like to help us?

                Awesome! Simply post in the forums using the link below and we'll get you started.

                Get Involved