Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Synchronet Synchronet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 262
    • Issues 262
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Admin message

This GitLab instance has migrated as of Nov-5-2022 to a new server: hardware, OS, SSH key

Admin message

The v3.20a development branch has now been merged to the master branch. Sysops upgrading from earlier versions must run 'jsexec update'

  • MainMain
  • SynchronetSynchronet
  • Issues
  • #129

Node 1 VDD Open failed (not loaded yet?)

Curiosity after Update

Just recently updated from the original 3.15b to the latest CVS as of jan 7. I had a couple of quirks I needed to iron out with the .js files. But nothing serious. I also notice this showing up in the control panel log. It never showed until the upgrade. Is this just because now the later version reports this or is it something I may have overlooked upon update..

  1/10  05:39:53p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:53p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:53p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:54p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:55p  Node 1 VDD Open failed (not loaded yet?)
  1/10  05:39:55p  Node 1 VDD Open failed (not loaded yet?)

This shows up during doors, but not all the time, Same door sometimes shows it, and sometimes not. The particular one above was when somebody went to upload a qwk .rep packet. It does not seem to hurt anything. I just had never had it before and was curious as to what it was.

Have a good One! Mike

---
 ■ Synchronet ■ The Holodeck BBS telnet://holo.homeip.net
Assignee
Assign to
Time tracking