Hi,
I have a Adobe Campaign instance configure where the tracking server and AC are running in the same Machine.
The redirection of the links works and also the /r/test call.
But the /log folder is not being created under redir and even I run the tracking workflow or run "nlserver tracking -instance:MYinstanceName -download -update" directly on the server none tracking record is being created.
I checked the webmdl.log and didn't find any issue.
And need some help, I'm quite blocked.
The version of AC is V7 build 8857
Thanks!
Solved! Go to Solution.
Hi All,
I was able to solve my issue.
First, i did a build upgrade from version 8857 to version 8984. This was necessary in my case to stop the errors when I opened or clicked an URL in the emails.
My mistake was that I was using the command /etc/init.d/nlserver 6 status to check all the processes that were launched and the output seemed correct, that is, trackinglogd was launched correctly.
But then i check using nlserver pdump and the feedback of this command was that trackinglogd was not started at all. Simply by launching the command nlserver start trackinglogd@default and restarting the server it worked.
With the trackinglogd up, the log folder in /redir was created and the tracking was collected successfully.
Hope this helps.
Kind regards,
Jose
Hi,
I am having the exact same issue but the difference is that the webmd.log is displaying errors when i Open or Click in an Email:
==> var/default/log/webmdl.log <==
2019-05-09 16:33:36.843Z 000000F0 000000F0 1 error log BAS-010018 Cannot create folder ‘/root/.appdata’ (errno=13, Permission denied) (iRc=-52)
2019-05-09 16:33:36.843Z 000000F0 000000F0 1 error log BAS-010015 Cannot open file ‘/root/.appdata/.shm_NlTrackingContext6.0Mutex’ with write access (errno=13, Permission denied) (iRc=-56)
2019-05-09 16:33:36.843Z 000000F0 000000F0 1 error log BAS-010035 Cannot write to file ‘/root/.appdata/.shm_NlTrackingContext6.0Mutex’ (errno=9, Bad file descriptor). (iRc=-52)
2019-05-09 16:33:36.843Z 000000F0 000000F0 1 error log BAS-010018 Cannot create folder ‘/root/.appdata’ (errno=13, Permission denied) (iRc=-52)
2019-05-09 16:33:36.843Z 000000F0 000000F0 1 error log BAS-010015 Cannot open file ‘/root/.appdata/.shm_NlTrackingContext6.0’ with write access (errno=13, Permission denied) (iRc=-56)
2019-05-09 16:33:36.844Z 000000F0 000000F0 1 error log BAS-010035 Cannot write to file ‘/root/.appdata/.shm_NlTrackingContext6.0’ (errno=9, Bad file descriptor). (iRc=-52)
2019-05-09 16:33:36.844Z 000000F0 000000F0 1 error log BAS-010018 Cannot create folder ‘/root/.appdata’ (errno=13, Permission denied) (iRc=-52)
2019-05-09 16:33:36.844Z 000000F0 000000F0 1 error log BAS-010015 Cannot open file ‘/root/.appdata/.shm_NlTrackingContext6.0’ with write access (errno=13, Permission denied) (iRc=-56)
2019-05-09 16:33:36.844Z 000000F0 000000F0 1 error log BAS-010035 Cannot write to file ‘/root/.appdata/.shm_NlTrackingContext6.0’ (errno=9, Bad file descriptor). (iRc=-52)
2019-05-09 16:33:36.844Z 000000F0 000000F0 1 error log SRV-810000 Impossible to allocate a shared memory block of identifier ‘NlTrackingContext6.0’ and of size 31700018 bytes. (iRc=-51)
Application server verison is 7.0 build 8857 as well.
florentlb Vipul Raghav Amit Kumar Adhiyan kirti.rawat Jean-Serge Biron
Thanks!
I am also facing the exact issue as faced by federicom24805345.
We are upgrading AC version from 6.1 to 6.7
The web and tracking modules are running on the same host:
(1)Tracked urls are correctly published at (/app/neolane/var/<INSTANCE>/redir/url/2019)
(2)Our redirection server is correctly setup. All tracked urls correctly redirect.
(3)Clicks are reaching apache logs correctly.
(4) Trackinglogd is running without any errors in the logs.
cml_qa2 2647131 1 0 02:40 pts/2 00:00:00 nlserver trackinglogd -tracefile:trackinglogd@default -instance:default -detach
(5)The tracking workflow under adobe campaign is also working and is not showing any error's in the log:
-- logs
05/15/2019 7:00:53 AM nlmodule Workflow finished
05/15/2019 7:00:51 AM nlmodule : 0 record(s) unchanged ('writer' step)
05/15/2019 7:00:51 AM nlmodule : updating 0 record(s) ('writer' step)
05/15/2019 7:00:51 AM nlmodule : Insertion of 1,203 record(s) 'writer' step)
05/15/2019 7:00:49 AM nlmodule 1,203 record(s) result from the union '' (step 'union')
05/15/2019 7:00:48 AM nlmodule 0 record(s) selected for the query '' (step 'trackinglog')
05/15/2019 7:00:48 AM nlmodule Executing union '' (step 'union')
05/15/2019 7:00:47 AM nlmodule 1,203 record(s) selected for the query '' (step 'broadlog')
05/15/2019 7:00:47 AM nlmodule Executing query '' (step 'trackinglog')
05/15/2019 7:00:46 AM nlmodule Executing query '' (step 'broadlog')
05/15/2019 7:00:42 AM nlmodule Consolidating tracking logs for the period [05/15/2019 1:25:00 AM, 05/15/2019 2:00:00 AM[...
05/15/2019 7:00:38 AM nlmodule Application server for Adobe Campaign Classic (7.0 18.4 build 8935@15402144) of 06/22/2018
05/15/2019 7:00:29 AM Workflow 'tracking' is being run
05/15/2019 6:28:54 AM nlmodule [42/42] record(s) processed (step 'writer')
BUT NO LOGS ARE GETTING GENERATED AT BELOW PATH - (/app/neolane/var/<INSTANCE>/redir/log/
Could someone pls help us to understand whether we need any configuration to tell trackinglogd process where to write logs? Thanks!
My case is similar as well, no logs are getting generated in .../var/<INSTANCE>/redir/log.
Main difference is the error log I posted before and that my tracking workflow finds no records to write even though it doesn't fail.
Can anyone please provide some insight at what could be happening to us??
Thanks!
Views
Replies
Total Likes
Hi All,
I was able to solve my issue.
First, i did a build upgrade from version 8857 to version 8984. This was necessary in my case to stop the errors when I opened or clicked an URL in the emails.
My mistake was that I was using the command /etc/init.d/nlserver 6 status to check all the processes that were launched and the output seemed correct, that is, trackinglogd was launched correctly.
But then i check using nlserver pdump and the feedback of this command was that trackinglogd was not started at all. Simply by launching the command nlserver start trackinglogd@default and restarting the server it worked.
With the trackinglogd up, the log folder in /redir was created and the tracking was collected successfully.
Hope this helps.
Kind regards,
Jose
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies