• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Stark

  • Rank


  • Gender
  • URL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If I recall, the progress bar is per file in the directory. Not ideal I know but I think that explains it. Davos was designed more as a “set it and leave it” app so the progress bar was a bit of an afterthought.
  2. What version of MySQL are you using? Is there anything in the logs?
  3. The logs suggest that you have multiple schedules running with the same filters/target directory. I could be mistaken as I’ve only scanned through the log. Also it seems that it’s not comparing the files from the last scan to find new files (it thinks it’s a first-time scan each time). It may be worth checking the scan list history to check it’s actually saving that reference after each run.
  4. Hi, Looking at the logs it seems that it did initially pick up the files based on the filter, but there was an error when attempting to download one of the metadata files. By default davos will try to continue with the workflow but will register all attempted files as having been actioned, so following runs of the schedule will ignore the files. That's why it appears the filter isn't working (it is, it's just ignoring them because it thinks it's seen them before). For some reason davos is unable to create the local directory for some sub folders when recursively downloa
  5. The downloaded files should take the ownership of the process owner so it could be you're running davos under the wrong PUID/PGID. That said I can't remember what permissions it sets on the files after downloading them. Double check your run configuration for the container so that the PUID and PGID match the user you want to take ownership of the files.
  6. @sickb0y It appears that there was a dependency change recently with OpenJRE which meant nss was no longer packaged up in its dependency tree. It has been added in manually now as part of the image build process. Hopefully this will fix your issue.
  7. That's just the app telling you that you've tried navigating to a page that doesn't exist. I don't believe I created an endpoint for /error, so it's falling back to that "white label" page.
  8. OK, we've figured out what went wrong. During the migration phase of our pipeline, the build command omitted a flag which set it to use production configuration. The result of this is that the latest image was build with a "staging" environment in mind and so had its database set in memory, not from a file. A new build has been pushed through the pipeline, so can you pull latest and check? You may find that now it looks for the database file correctly, it will pick up your old existing database, so will be a bit stale. Long story short: we dropped the ball a bit with t
  9. @manofcolombia Sorry mate it's been a hectic week. I'll try and have a look at the latest tag in the next couple of days. In the meantime, switch back from ":latest" and use ":2.2.1" instead. That was the version of the app before we migrated our pipeline. Can you see if this helps; if so we know it's an issue with the latest build of the Docker image.
  10. @drumstyx at this point if you're putting effort into using rclone instead, just keep using that. I'm afraid I don't have any more free time to give to this project as I recently took a new job which has effectively exhausted me. Parallel downloads won't be something I personally implement. @manofcolombia nothing has changed regarding the actual application but I will check to see if anything has changed regarding the image dependencies.
  11. Hi @drumstyx, when you say you're getting a 24Mbit/s transfer speed, are you referring to actual speeds? I have a 74Mbit/s line, and when using davos, got ~6.5MB/s - which isn't too far off 80-90% of my available bandwidth. Admittedly I've not run the application on a faster line (they're just not available to me where I live). I appreciate that the slowness for some people is annoying, but my implementation of the FTP and SFTP libraries is incredibly basic (practically no internal library tweaking), as the davos application was initially designed as a personal project that ended u
  12. Hi guys, sorry for the late reply. I have to admit this isn't something I've noticed. I haven't released to davos since 1st Oct 2017 so any differences in performance would be either externally instigated, or perhaps via the Docker image (although I can't see this being the cause). The best I can offer in terms of help is the suggestion to keep monitoring it and seeing how it goes. My implementation of the connection speed can be a bit flaky for SFTP connections so it may be that while it shows a slow speed, it's not necessarily that slow. Are you able to monitor the t
  13. Hi @sinbrkatetete, there is currently no support for connecting to a host via proxies (SOCKS or HTTP). If this is something you would like to have, please add a request as an Issue in GitHub (, with your requirements so I can see if this is something I can add in to a future version. Cheers!
  14. If for example your host machine has the following directory structure: / home/ downloads/ tmp/ other/ And the docker container has the following internal structure: / download/ tmp/ app/ When you map your directories during the creation process ("-v /home/downloads:/download"), you do this: / / home/ downloads/ <-------------------> download/ tmp/ tmp/ other/ app/ That link (or, mapping) effective
  15. Hi @Nyghthawk, davos does not assume where your "download" folder is, as it was designed to be relatively flexible regarding which directories you wish for it to be aware of. Due to the way Docker containers work, it is important to remember that just by mapping /home/my/host/directory:/download you are not telling davos (the application) where you want downloaded files to go. All that does is tell the Docker container where you want files in the internal /download directory to be on your host. For example, if you decided to run davos natively on your machine, you'd tel