Got errors in my seafile.log and seahub.log?

Hi,
I did take a look in my .log files and it seem that I have some errors but I have not been affected by it as far as I can tell.

seafile.log
I do have a couple of this and every one seem to have the same repo no.

[06/30/17 16:19:31] size-sched.c(246): [scheduler] failed to get repo dbe95127-353a-4cd8-a1f8-0584e7eb402f.
[06/30/17 16:19:31] upload-file.c(300): [upload] Failed to get repo dbe95127.

[06/30/17 16:24:14] size-sched.c(246): [scheduler] failed to get repo dbe95127-353a-4cd8-a1f8-0584e7eb402f.

after [07/01/17 08:02:47] they have not shown again.

seahub.log
I do have many of this:

2017-07-01 06:45:32,843 [ERROR] seahub.api2.endpoints.repo_file_uploaded_bytes:64 get 'SeafileAPI' object has no attribute 'get_upload_tmp_file_offset'

it startes 2017-07-01 05:51:41 and after 2017-07-01 05:51:41 I have not seen it anymore.

Also got a bunch of this:

2017-06-30 13:03:31,942 [ERROR] seahub.thumbnail.utils:128 generate_thumbnail cannot identify image file <StringIO.StringIO instance at 0x7ff861aee5a8>

Did stop show in the log after 2017-06-30 13:03:32.

and this:

2017-07-01 09:28:15,592 [ERROR] seahub.thumbnail.utils:128 generate_thumbnail broken data stream when reading image file

After 2017-07-01 09:33:23 they did stop showing in the log.

I did run fsck and I don’t think it did find any errors or?

Starting seaf-fsck, please wait ...

[07/01/17 12:44:59] fsck.c(595): Running fsck for repo e10babcf-e4b8-4129-8275-0                              036637cf7e8.
[07/01/17 12:44:59] fsck.c(422): Checking file system integrity of repo My Libra                              ry Template(e10babcf)...
[07/01/17 12:44:59] fsck.c(659): Fsck finished for repo e10babcf.

[07/01/17 12:44:59] fsck.c(595): Running fsck for repo d4ae6143-14cf-4096-b5b9-1                              fb962021c05.
[07/01/17 12:44:59] fsck.c(422): Checking file system integrity of repo Desktop(                              d4ae6143)...
[07/01/17 12:45:01] fsck.c(659): Fsck finished for repo d4ae6143.

[07/01/17 12:45:01] fsck.c(595): Running fsck for repo a9d3c76e-60a3-4b33-ae58-1                              15cf32778d8.
[07/01/17 12:45:01] fsck.c(422): Checking file system integrity of repo Dokument                              (a9d3c76e)...
[07/01/17 12:45:01] fsck.c(659): Fsck finished for repo a9d3c76e.

[07/01/17 12:45:01] fsck.c(595): Running fsck for repo 9e53f635-a2b6-4949-b2be-4                              f073d5538e5.
[07/01/17 12:45:01] fsck.c(422): Checking file system integrity of repo Pictures                              (9e53f635)...
[07/01/17 12:47:19] fsck.c(659): Fsck finished for repo 9e53f635.

[07/01/17 12:47:19] fsck.c(595): Running fsck for repo 914a07c8-cac6-4011-9de5-d                              6eb00694c4b.
[07/01/17 12:47:19] fsck.c(422): Checking file system integrity of repo Mitt bib                              liotek(914a07c8)...
[07/01/17 12:47:19] fsck.c(659): Fsck finished for repo 914a07c8.

[07/01/17 12:47:19] fsck.c(595): Running fsck for repo 51d0a2cb-7b70-4589-9b55-2                              4c04148245b.
[07/01/17 12:47:19] fsck.c(422): Checking file system integrity of repo My Libra                              ry(51d0a2cb)...
[07/01/17 12:47:19] fsck.c(659): Fsck finished for repo 51d0a2cb.

[07/01/17 12:47:19] fsck.c(595): Running fsck for repo 0a860c7a-3ecf-4c30-bab5-0                              3132a1e7222.
[07/01/17 12:47:19] fsck.c(422): Checking file system integrity of repo Digitalk                              amera(0a860c7a)...
[07/01/17 12:47:45] fsck.c(659): Fsck finished for repo 0a860c7a.

[07/01/17 12:47:45] fsck.c(595): Running fsck for repo 0652eb54-cec6-42a4-b4f6-d                              64d41222f48.
[07/01/17 12:47:45] fsck.c(422): Checking file system integrity of repo Bilder(0                              652eb54)...
[07/01/17 12:50:37] fsck.c(659): Fsck finished for repo 0652eb54.

[07/01/17 12:50:37] fsck.c(595): Running fsck for repo 02ceee32-c543-40a2-bc32-7a8f8c6b7fe4.
[07/01/17 12:50:37] fsck.c(422): Checking file system integrity of repo Documents(02ceee32)...
[07/01/17 12:51:02] fsck.c(659): Fsck finished for repo 02ceee32.

seaf-fsck run done

Done.

So should I bee worried, can I fix it anyway?

Edit:
Just to bee clear I did use the CE version when this logs was created, I’m using the Pro version now - don’t know if I’ll get this kind of errors now as they have stoped this morning etc. but still I’m confused regarding the errors.
So why did I get them?