Backup agent for Linux servers and workstations on-premises or in the public cloud
Post Reply
jmaier74
Lurker
Posts: 1
Liked: never
Joined: Jan 22, 2018 8:06 am
Full Name: Jörg Maier
Contact:

Feature Request forwarding Messages to dedicated Logfile

Post by jmaier74 » Jan 22, 2018 9:05 am

Hello Dev Team,

is it possible to redirect Veeam Agent for Linux Messages to a dedicated Logfile?
The messages from Veeam Agent for Linux in demsg/messages gets importand messages lost.

Regards
Joerg

vmniels
Veeam Software
Posts: 1968
Liked: 430 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by vmniels » Jan 22, 2018 8:27 pm

I haven't looked into it but I think u can use the default rsyslog or syslog-ng for getting the messages out of dmesg. I will see if I can get this working and report back.
VCP-DCV
Veeam Certified Architect (VMCA)
http://foonet.be

PTide
Veeam Software
Posts: 4233
Liked: 348 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by PTide » Jan 23, 2018 2:37 pm

Hi,

BTW, a separate logfile for Agent driver is already on the list of future improvements.

Thanks

Hejah
Influencer
Posts: 13
Liked: 1 time
Joined: Mar 20, 2018 4:08 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by Hejah » Sep 07, 2018 11:11 am

Hallo,
I am looking forward to this feature. Currently more than 95% of the demsg entries are generated by Veeam.

Meanwhile, is it possible to reduce the amount of entry's which is written to demsg/syslog?

Changing the ([veeamsnap]) debuglogging entry in /etc/veeam/veeam.ini does not seem to have any effect on thus log entry.

Thanks

PTide
Veeam Software
Posts: 4233
Liked: 348 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by PTide » Sep 07, 2018 4:15 pm

Hi,

Setting "2" as a value for debuglogging parameter should prevent the module from writing messages into dmesg completely. In order for changes to take effect you should unload and load the module after changes.

Thanks

Hejah
Influencer
Posts: 13
Liked: 1 time
Joined: Mar 20, 2018 4:08 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by Hejah » Sep 11, 2018 2:59 pm

Hi,
after changing it
/etc/veeam/veeam.ini

Code: Select all

[veeamsnap]
# Kernel log logging level. 7 - list all messages as an error, 4 or 0 - all messages as a warning, 2 - all message as a trace (use only if veeam works perfectly on your system)
debuglogging= 2
and reloading the kernel module

Code: Select all

systemctl stop veeamservice.service
modprobe -r veeamsnap
lsmod | grep veeam
modprobe veeamsnap
systemctl start veeamservice.service
and running a veeam (Version v2.0.1.665) backup, I get still a lot of entries in dmesg/syslog

Thanks

PTide
Veeam Software
Posts: 4233
Liked: 348 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by PTide » Sep 11, 2018 5:24 pm

Checked with the dev team, please try the following:

1. Unload the module
2. unload the service
3. make changes to veeam.ini
4. start the service

Also please post the first lines of messages that appear in the dmesg right after the module starts - it should show the parameters it starts with.

Thanks

Hejah
Influencer
Posts: 13
Liked: 1 time
Joined: Mar 20, 2018 4:08 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by Hejah » Sep 14, 2018 8:12 am

Sorry for my late reply,

Code: Select all

modprobe -r veeamsnap
systemctl stop veeamservice.service
nano /etc/veeam/veeam.ini
systemctl start veeamservice.service
after that I got no dmesg entry's from veeam.

At the start of an backup I get the flowing entry's

Code: Select all

[ 1733.147325] FS-Cache: Loaded
[ 1733.162387] FS-Cache: Netfs 'nfs' registered for caching
[ 1733.182380] NFS: Registering the id_resolver key type
[ 1733.182389] Key type id_resolver registered
[ 1733.182390] Key type id_legacy registered
[ 1735.967384] veeamsnap: loading out-of-tree module taints kernel.
[ 1735.967474] veeamsnap: module verification failed: signature and/or required key missing - tainting kernel
[ 1735.968392]     veeamsnap:veeamsnap_init Loading
[ 1735.968393]     veeamsnap:veeamsnap_init Version: 2.0.1.665
[ 1735.968394]     veeamsnap:veeamsnap_init Author: Veeam Software AG
[ 1735.968395]     veeamsnap:veeamsnap_init licence: GPL
[ 1735.968396]     veeamsnap:veeamsnap_init description: Veeam Snapshot Kernel Module
[ 1735.968397]     veeamsnap:veeamsnap_init zerosnapdata: 1
[ 1735.968398]     veeamsnap:veeamsnap_init debuglogging: 2
[ 1735.968398]     veeamsnap:veeamsnap_init snapstore enabled
[ 1735.968399]     veeamsnap:veeamsnap_init start. container_alloc_counter=0
[ 1735.968400]     veeamsnap:veeamsnap_init start. container_sl_alloc_counter=0
[ 1735.968401]     veeamsnap:veeamsnap_init start. mem_cnt=0
[ 1735.968402]     veeamsnap:veeamsnap_init start. vmem_cnt=0
[ 1735.968403]     veeamsnap:ctrl_pipe_init .
[ 1735.968406]     veeamsnap:veeamsnap_init Module major=242
[ 1735.968479]     veeamsnap:blk_direct_bioset_create Specific bio set created.
[ 1735.968532]     veeamsnap:blk_redirect_bioset_create Specific bio set created.
[ 1735.968654]     veeamsnap:blk_deferred_bioset_create Specific bio set created.
[ 1735.968658]     veeamsnap:snapimage_init .
[ 1735.968659]     veeamsnap:snapimage_init Snapimage block device was registered. major=252
[ 1735.968660]     veeamsnap:veeamsnap_init end. container_alloc_counter=0
[ 1735.968661]     veeamsnap:veeamsnap_init end. container_sl_alloc_counter=0
[ 1735.968662]     veeamsnap:veeamsnap_init end. mem_cnt=1
[ 1735.968663]     veeamsnap:veeamsnap_init end. vmem_cnt=0
[ 1735.971817]     veeamsnap:ctrl_open file=0x00000000f6967f57
[ 1735.971843]     veeamsnap:ioctl_compatibility_flags Get compatibility flags
[ 1735.971913]     veeamsnap:ioctl_tracking_collect Collecting tracking device:
[ 1735.971918]     veeamsnap:tracking_collect Have not device under CBT.
[ 1735.973517]     veeamsnap:tracking_add Adding. dev_id=8:1
[ 1735.973523]     veeamsnap:tracker_Create dev_id 8:1
[ 1735.973525]     veeamsnap:tracker_Create SectorStart    =0x800
[ 1735.973526]     veeamsnap:tracker_Create SectorsCapacity=0x100000
[ 1735.973527]     veeamsnap:tracker_cbt_start .
[ 1735.973528]     veeamsnap:cbt_map_create CBT map create.
[ 1736.041596]     veeamsnap:tracker_Create freezed
[ 1736.041599]     veeamsnap:tracker_queue_Ref Creating tracker_queue for queue=0x00000000b2f4d781
[ 1736.041602]     veeamsnap:tracker_queue_Ref Tracker queue created. pTrQ=0x00000000febea72a
....
and a lot more whil Veeam is creating the backup.

And with the steps from last time

Code: Select all

systemctl stop veeamservice.service
modprobe -r veeamsnap
nano /etc/veeam/veeam.ini
modprobe veeamsnap
systemctl start veeamservice.service
I get the following output without starting a backup:

Code: Select all

[ 3067.294346]     veeamsnap:veeamsnap_exit Module unloaded. Major=242
[ 3091.231598]     veeamsnap:veeamsnap_init Loading
[ 3091.231600]     veeamsnap:veeamsnap_init Version: 2.0.1.665
[ 3091.231601]     veeamsnap:veeamsnap_init Author: Veeam Software AG
[ 3091.231602]     veeamsnap:veeamsnap_init licence: GPL
[ 3091.231602]     veeamsnap:veeamsnap_init description: Veeam Snapshot Kernel Module
[ 3091.231603]     veeamsnap:veeamsnap_init zerosnapdata: 0
[ 3091.231604]     veeamsnap:veeamsnap_init debuglogging: 0
[ 3091.231605]     veeamsnap:veeamsnap_init snapstore enabled
[ 3091.231606]     veeamsnap:veeamsnap_init start. container_alloc_counter=0
[ 3091.231607]     veeamsnap:veeamsnap_init start. container_sl_alloc_counter=0
[ 3091.231607]     veeamsnap:veeamsnap_init start. mem_cnt=0
[ 3091.231608]     veeamsnap:veeamsnap_init start. vmem_cnt=0
[ 3091.231609]     veeamsnap:ctrl_pipe_init .
[ 3091.231612]     veeamsnap:veeamsnap_init Module major=242
[ 3091.231679]     veeamsnap:blk_direct_bioset_create Specific bio set created.
[ 3091.231722]     veeamsnap:blk_redirect_bioset_create Specific bio set created.
[ 3091.231911]     veeamsnap:blk_deferred_bioset_create Specific bio set created.
[ 3091.231919]     veeamsnap:snapimage_init .
[ 3091.231921]     veeamsnap:snapimage_init Snapimage block device was registered. major=252
[ 3091.231922]     veeamsnap:veeamsnap_init end. container_alloc_counter=0
[ 3091.231923]     veeamsnap:veeamsnap_init end. container_sl_alloc_counter=0
[ 3091.231923]     veeamsnap:veeamsnap_init end. mem_cnt=1
[ 3091.231924]     veeamsnap:veeamsnap_init end. vmem_cnt=0
At the start of an backup I get then the flowing entry's

Code: Select all

[ 3569.660012]     veeamsnap:ctrl_open file=0x00000000a81c8162
[ 3569.660049]     veeamsnap:ioctl_compatibility_flags Get compatibility flags
[ 3569.660134]     veeamsnap:ioctl_tracking_collect Collecting tracking device:
[ 3569.660138]     veeamsnap:tracking_collect Have not device under CBT.
[ 3569.661953]     veeamsnap:tracking_add Adding. dev_id=8:1
[ 3569.661960]     veeamsnap:tracker_Create dev_id 8:1
[ 3569.661962]     veeamsnap:tracker_Create SectorStart    =0x800
[ 3569.661963]     veeamsnap:tracker_Create SectorsCapacity=0x100000
[ 3569.661964]     veeamsnap:tracker_cbt_start .
[ 3569.661965]     veeamsnap:cbt_map_create CBT map create.
[ 3569.740895]     veeamsnap:tracker_Create freezed
[ 3569.740900]     veeamsnap:tracker_queue_Ref Creating tracker_queue for queue=0x00000000b2f4d781
[ 3569.740904]     veeamsnap:tracker_queue_Ref Tracker queue created. pTrQ=0x00000000ded660ab
[ 3569.740907]     veeamsnap:tracker_Create thawed.
[ 3569.740988]     veeamsnap:tracking_add Adding. dev_id=8:2
[ 3569.740997]     veeamsnap:tracker_Create dev_id 8:2
[ 3569.740998]     veeamsnap:tracker_Create SectorStart    =0x100800
[ 3569.741000]     veeamsnap:tracker_Create SectorsCapacity=0xf4000
[ 3569.741001]     veeamsnap:tracker_cbt_start .
[ 3569.741003]     veeamsnap:cbt_map_create CBT map create.
[ 3569.829489]     veeamsnap:tracker_Create freezed
[ 3569.829492]     veeamsnap:tracker_queue_Ref Queue already exist! queue=0x0x00000000b2f4d781
...

Thanks

PTide
Veeam Software
Posts: 4233
Liked: 348 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by PTide » Sep 14, 2018 12:35 pm

It seems that after you've specified "2", the agent prints messages on info(6) level. It might be that you have default level set to "7". Please try setting it to "4" or "3", for example:

Code: Select all

echo 4 > /proc/sys/kernel/printk
Thanks

Hejah
Influencer
Posts: 13
Liked: 1 time
Joined: Mar 20, 2018 4:08 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by Hejah » Sep 14, 2018 2:32 pm

The default is 4 on the system:

Code: Select all

cat /proc/sys/kernel/printk
4	4	1	7
and setting it to 3 didn't change anything

Code: Select all

systemctl stop veeamservice.service
modprobe -r veeamsnap
echo 3 > /proc/sys/kernel/printk
nano /etc/veeam/veeam.ini
modprobe veeamsnap
systemctl start veeamservice.service
cat /proc/sys/kernel/printk
3	4	1	7

Code: Select all

[25993.063997]     veeamsnap:veeamsnap_init Loading
[25993.063999]     veeamsnap:veeamsnap_init Version: 2.0.1.665
[25993.064000]     veeamsnap:veeamsnap_init Author: Veeam Software AG
[25993.064001]     veeamsnap:veeamsnap_init licence: GPL
[25993.064003]     veeamsnap:veeamsnap_init description: Veeam Snapshot Kernel Module
[25993.064004]     veeamsnap:veeamsnap_init zerosnapdata: 0
[25993.064005]     veeamsnap:veeamsnap_init debuglogging: 0
[25993.064006]     veeamsnap:veeamsnap_init snapstore enabled
[25993.064007]     veeamsnap:veeamsnap_init start. container_alloc_counter=0
[25993.064008]     veeamsnap:veeamsnap_init start. container_sl_alloc_counter=0
[25993.064010]     veeamsnap:veeamsnap_init start. mem_cnt=0
[25993.064011]     veeamsnap:veeamsnap_init start. vmem_cnt=0
[25993.064012]     veeamsnap:ctrl_pipe_init .
[25993.064015]     veeamsnap:veeamsnap_init Module major=242
[25993.064125]     veeamsnap:blk_direct_bioset_create Specific bio set created.
[25993.064188]     veeamsnap:blk_redirect_bioset_create Specific bio set created.
[25993.064257]     veeamsnap:blk_deferred_bioset_create Specific bio set created.
[25993.064266]     veeamsnap:snapimage_init .
[25993.064268]     veeamsnap:snapimage_init Snapimage block device was registered. major=252
[25993.064270]     veeamsnap:veeamsnap_init end. container_alloc_counter=0
[25993.064271]     veeamsnap:veeamsnap_init end. container_sl_alloc_counter=0
[25993.064272]     veeamsnap:veeamsnap_init end. mem_cnt=1
[25993.064273]     veeamsnap:veeamsnap_init end. vmem_cnt=0

Code: Select all

cat /proc/sys/kernel/printk
3	4	1	7
veeam

Code: Select all

[26157.669090]     veeamsnap:ctrl_open file=0x00000000c83e293c
[26157.669141]     veeamsnap:ioctl_compatibility_flags Get compatibility flags
[26157.669221]     veeamsnap:ioctl_tracking_collect Collecting tracking device:
[26157.669226]     veeamsnap:tracking_collect Have not device under CBT.
[26157.670995]     veeamsnap:tracking_add Adding. dev_id=8:1
[26157.671003]     veeamsnap:tracker_Create dev_id 8:1
[26157.671004]     veeamsnap:tracker_Create SectorStart    =0x800
[26157.671005]     veeamsnap:tracker_Create SectorsCapacity=0x100000
[26157.671007]     veeamsnap:tracker_cbt_start .
[26157.671008]     veeamsnap:cbt_map_create CBT map create.
[26157.735835]     veeamsnap:tracker_Create freezed
[26157.735840]     veeamsnap:tracker_queue_Ref Creating tracker_queue for queue=0x00000000b2f4d781
[26157.735843]     veeamsnap:tracker_queue_Ref Tracker queue created. pTrQ=0x00000000e0bdc505
[26157.735846]     veeamsnap:tracker_Create thawed.
[26157.735949]     veeamsnap:tracking_add Adding. dev_id=8:2
[26157.735958]     veeamsnap:tracker_Create dev_id 8:2
[26157.735959]     veeamsnap:tracker_Create SectorStart    =0x100800
[26157.735961]     veeamsnap:tracker_Create SectorsCapacity=0xf4000
[26157.735962]     veeamsnap:tracker_cbt_start .
[26157.735964]     veeamsnap:cbt_map_create CBT map create.
[26157.800427]     veeamsnap:tracker_Create freezed
[26157.800431]     veeamsnap:tracker_queue_Ref Queue already exist! queue=0x0x00000000b2f4d781
[26157.800986]     veeamsnap:tracker_Create thawed.
[26157.801076]     veeamsnap:tracking_add Adding. dev_id=253:1
[26157.801081]     veeamsnap:tracker_Create dev_id 253:1
Thanks

PTide
Veeam Software
Posts: 4233
Liked: 348 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Feature Request forwarding Messages to dedicated Logfile

Post by PTide » Sep 18, 2018 8:32 pm

Although you've configured everything correctly, it still does not work as intended. At this point I have no other option than to admit that it must be a bug. I've asked our QA team to confirm it so it can be fixed. In case they don't manage to confirm, I'll reach back to you to get more info and to ask you to provide some logs.

Thank you for your help.

Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests