[jira] [Created] (TS-1858) Redefinition of timersub on OmniOS with the ESI plugin
Daniel Gruno created TS-1858: Summary: Redefinition of timersub on OmniOS with the ESI plugin Key: TS-1858 URL: https://issues.apache.org/jira/browse/TS-1858 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Daniel Gruno On OmniOS, timersub is already defined in sys/time.h, but we seem to think it's not, since it's a Solaris derived system, and thus we get: Making all in esi gmake[3]: Entering directory `/var/jenkins/workspace/master_omnios_x64/plugins/experimental/esi' CXXDocNode.lo CXXEsiParser.lo CXXEsiGzip.lo CXXEsiProcessor.lo In file included from lib/EsiProcessor.cc:26:0: lib/FailureInfo.h:31:0: error: timersub redefined [-Werror] /usr/include/sys/time.h:169:0: note: this is the location of the previous definition cc1plus: all warnings being treated as errors gmake[3]: *** [EsiProcessor.lo] Error 1 This should be fixed by checking for the existence of the definition before (re)defining it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-1858) Redefinition of timersub on OmniOS with the ESI plugin
[ https://issues.apache.org/jira/browse/TS-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gruno reassigned TS-1858: Assignee: Daniel Gruno Redefinition of timersub on OmniOS with the ESI plugin -- Key: TS-1858 URL: https://issues.apache.org/jira/browse/TS-1858 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Daniel Gruno Assignee: Daniel Gruno On OmniOS, timersub is already defined in sys/time.h, but we seem to think it's not, since it's a Solaris derived system, and thus we get: Making all in esi gmake[3]: Entering directory `/var/jenkins/workspace/master_omnios_x64/plugins/experimental/esi' CXXDocNode.lo CXXEsiParser.lo CXXEsiGzip.lo CXXEsiProcessor.lo In file included from lib/EsiProcessor.cc:26:0: lib/FailureInfo.h:31:0: error: timersub redefined [-Werror] /usr/include/sys/time.h:169:0: note: this is the location of the previous definition cc1plus: all warnings being treated as errors gmake[3]: *** [EsiProcessor.lo] Error 1 This should be fixed by checking for the existence of the definition before (re)defining it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-1858) Redefinition of timersub on OmniOS with the ESI plugin
[ https://issues.apache.org/jira/browse/TS-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gruno resolved TS-1858. -- Resolution: Fixed fix works~ Redefinition of timersub on OmniOS with the ESI plugin -- Key: TS-1858 URL: https://issues.apache.org/jira/browse/TS-1858 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Daniel Gruno Assignee: Daniel Gruno On OmniOS, timersub is already defined in sys/time.h, but we seem to think it's not, since it's a Solaris derived system, and thus we get: Making all in esi gmake[3]: Entering directory `/var/jenkins/workspace/master_omnios_x64/plugins/experimental/esi' CXXDocNode.lo CXXEsiParser.lo CXXEsiGzip.lo CXXEsiProcessor.lo In file included from lib/EsiProcessor.cc:26:0: lib/FailureInfo.h:31:0: error: timersub redefined [-Werror] /usr/include/sys/time.h:169:0: note: this is the location of the previous definition cc1plus: all warnings being treated as errors gmake[3]: *** [EsiProcessor.lo] Error 1 This should be fixed by checking for the existence of the definition before (re)defining it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1663) gitpubsub comments test
Daniel Gruno created TS-1663: Summary: gitpubsub comments test Key: TS-1663 URL: https://issues.apache.org/jira/browse/TS-1663 Project: Traffic Server Issue Type: Test Reporter: Daniel Gruno This is merely an issue set up to test the git - jira hook we are planning to use. nothing to see here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TS-1064) logging format update
[ https://issues.apache.org/jira/browse/TS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gruno closed TS-1064. So yeah, I should've closed this issue long ago. logging format update - Key: TS-1064 URL: https://issues.apache.org/jira/browse/TS-1064 Project: Traffic Server Issue Type: Task Components: Documentation Reporter: Zhao Yongming Assignee: Daniel Gruno Priority: Trivial Fix For: Doc 3.2 %phi is not documented so far, we should make sure all those hiding items documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-993) Add OpenBSD support.
[ https://issues.apache.org/jira/browse/TS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gruno updated TS-993: Attachment: freebsd.patch Patch that fixes the broken loop in Log.cc that makes ATS fail during debug mode and consume 100% cpu Add OpenBSD support. Key: TS-993 URL: https://issues.apache.org/jira/browse/TS-993 Project: Traffic Server Issue Type: Improvement Environment: OpenBSD Reporter: Piotr Sikora Fix For: 3.3.1 Attachments: 0001-Add-OpenBSD-support.patch, freebsd.patch Add OpenBSD support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-993) Add OpenBSD support.
[ https://issues.apache.org/jira/browse/TS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13456557#comment-13456557 ] Daniel Gruno commented on TS-993: - The same bug applies to FreeBSD, as reported at http://www.freebsd.org/cgi/query-pr.cgi?pr=170829 Issues 1, 2 and 3 are related to a mutex not being locked/acquired (according to FreeBSD at least, I'll have to make sure) in Log.cc and subsequently being told to do an ink_cond_wait (which fails with EPERM and thus causes it to loop forever without waiting). I'm attaching a patch that fixes this issue. Add OpenBSD support. Key: TS-993 URL: https://issues.apache.org/jira/browse/TS-993 Project: Traffic Server Issue Type: Improvement Environment: OpenBSD Reporter: Piotr Sikora Fix For: 3.3.1 Attachments: 0001-Add-OpenBSD-support.patch, freebsd.patch Add OpenBSD support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-1064) logging format update
[ https://issues.apache.org/jira/browse/TS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gruno resolved TS-1064. -- Resolution: Fixed As there has been no objections, I'm closing this issue as fixed. If anyone feels otherwise, feel free to reopen. logging format update - Key: TS-1064 URL: https://issues.apache.org/jira/browse/TS-1064 Project: Traffic Server Issue Type: Task Components: Documentation Reporter: Zhao Yongming Assignee: Daniel Gruno Priority: Trivial Fix For: Doc 3.2 %phi is not documented so far, we should make sure all those hiding items documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-993) Add OpenBSD support.
[ https://issues.apache.org/jira/browse/TS-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13456675#comment-13456675 ] Daniel Gruno commented on TS-993: - ink_mutex_try_acquire would be just as peachy for me, and probably a safer bet. I did try using the 'try' version myself, and got the same good results (ie cpu not rising to 100%). Add OpenBSD support. Key: TS-993 URL: https://issues.apache.org/jira/browse/TS-993 Project: Traffic Server Issue Type: Improvement Environment: OpenBSD Reporter: Piotr Sikora Fix For: 3.3.1 Attachments: 0001-Add-OpenBSD-support.patch, freebsd.patch Add OpenBSD support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-1064) logging format update
[ https://issues.apache.org/jira/browse/TS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gruno reassigned TS-1064: Assignee: Daniel Gruno (was: Zhao Yongming) logging format update - Key: TS-1064 URL: https://issues.apache.org/jira/browse/TS-1064 Project: Traffic Server Issue Type: Task Components: Documentation Reporter: Zhao Yongming Assignee: Daniel Gruno Priority: Trivial Fix For: Doc 3.2 %phi is not documented so far, we should make sure all those hiding items documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1064) logging format update
[ https://issues.apache.org/jira/browse/TS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13452853#comment-13452853 ] Daniel Gruno commented on TS-1064: -- I added %phi among some other missing items last Friday (although the buildbot servers were down at the time, so it only took effect a few days later). Can someone confirm that %phi does what I seem to think it does, so we can close this? :) http://trafficserver.apache.org/docs/trunk/admin/event-logging-formats/index.en.html There's also %crat and some other new things. logging format update - Key: TS-1064 URL: https://issues.apache.org/jira/browse/TS-1064 Project: Traffic Server Issue Type: Task Components: Documentation Reporter: Zhao Yongming Assignee: Daniel Gruno Priority: Trivial Fix For: Doc 3.2 %phi is not documented so far, we should make sure all those hiding items documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1444) Cache Inspector has a few bugs in it
Daniel Gruno created TS-1444: Summary: Cache Inspector has a few bugs in it Key: TS-1444 URL: https://issues.apache.org/jira/browse/TS-1444 Project: Traffic Server Issue Type: Bug Components: Cache, Web UI Affects Versions: 3.3.0 Environment: FreeBSD 9 Reporter: Daniel Gruno Priority: Minor I seem to have stumbled upon a few bugs with the Cache Inspector Web UI - I'll bundle them in this ticket, for your annoyance :) First of all, the titles of the lookup pages seem to have font and /font in them, which should probably be fixed - see f.x. http://dallas.awesomelysecure.org/myCI/lookup_url?url=http%3A%2F%2Fwww.humbedooh.com%2F Secondly, the lookup doesn't work. I have my sites set to cache elements for 2 hours (revalidate=2h), but neither the regular lookup nor the regex lookup seem to return any cached results for my site. I even tried looking up .* in the regex version, but to no avail. Am I doing something wrong (or missing a configuration) since this doesn't work, or is this a bug or a missing/incomplete feature? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1064) logging format update
[ https://issues.apache.org/jira/browse/TS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449549#comment-13449549 ] Daniel Gruno commented on TS-1064: -- Just took a look at Log.cc - shouldn't have done that ;) There is a ton of logging options we haven't documented yet. I'll take a stab at (at least) adding the options to the documentation and the log builder tomorrow, if no one beats me to it. logging format update - Key: TS-1064 URL: https://issues.apache.org/jira/browse/TS-1064 Project: Traffic Server Issue Type: Task Components: Documentation Reporter: Zhao Yongming Assignee: Zhao Yongming Priority: Trivial Fix For: Doc 3.2 %phi is not documented so far, we should make sure all those hiding items documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1438) Cache inspector should add trailing slash to CI URL
Daniel Gruno created TS-1438:
Summary: Cache inspector should add trailing slash to CI URL
Key: TS-1438
URL: https://issues.apache.org/jira/browse/TS-1438
Project: Traffic Server
Issue Type: Bug
Components: Web UI
Affects Versions: 3.3.0
Environment: FreeBSD 9.0
Reporter: Daniel Gruno
Priority: Trivial
When setting up the Cache Inspector as described by the docs
(http://trafficserver.apache.org/docs/trunk/admin/configuring-cache/index.en.html
), an URL snafooey occurs.
In remap.config I have set:
map http://dallas.awesomelysecure.org/myCI http://{cache} @action=allow
When accessing /myCI, I do get the cache inspector, but because it fails to add
a trailing slash, the links are all broken, pointing to f.x. /lookup_url
instead of /myCI/lookup_url.
This could be solved by checking if a trailing slash exists, and if not,
issuing a 301 redirect to /myCI/.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1064) logging format update
[ https://issues.apache.org/jira/browse/TS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449302#comment-13449302 ] Daniel Gruno commented on TS-1064: -- phi = Proxy Host IP Am I correct in assuming this is the same as %phn, just the IP instead of the host name? If so, it's an easy fix. logging format update - Key: TS-1064 URL: https://issues.apache.org/jira/browse/TS-1064 Project: Traffic Server Issue Type: Task Components: Documentation Reporter: Zhao Yongming Assignee: Zhao Yongming Priority: Trivial Fix For: Doc 3.2 %phi is not documented so far, we should make sure all those hiding items documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1234) 404 link (and incorrect instructions) on document records.config.html in trunk
[ https://issues.apache.org/jira/browse/TS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449313#comment-13449313 ] Daniel Gruno commented on TS-1234: -- Pinging as I don't like 404s - should the instruction just be scrapped, or do we have new instructions for this? 404 link (and incorrect instructions) on document records.config.html in trunk -- Key: TS-1234 URL: https://issues.apache.org/jira/browse/TS-1234 Project: Traffic Server Issue Type: Bug Components: Documentation Affects Versions: Doc 3.0 Environment: Web Browser Reporter: Michael Turner Priority: Minor This URL: http://trafficserver.apache.org/docs/trunk/admin/configuration-files/records.config.en.html Has a broken link in the Security section, in this sentence: Important: If you enable this option, then you must also specify a filtering rule in the filter.config file to allow only certain machines to push content into the cache. The link to filter.config is 404. This file doesn't exist anymore, per Leif, so it's probably a safe bet this instruction is wrong, too. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-694) Alternate Languages needs to be translated too.
[ https://issues.apache.org/jira/browse/TS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449328#comment-13449328 ] Daniel Gruno commented on TS-694: - The original comment is a bit vague on where this problem exists (Hi, I'm new in class!). Is this fixed aka not an issue in 3.0 - does it even apply to 3.0? I can't seem to find any Alternate Languages stuff in the 3.0 docs at least. Alternate Languages needs to be translated too. - Key: TS-694 URL: https://issues.apache.org/jira/browse/TS-694 Project: Traffic Server Issue Type: Bug Components: Documentation Affects Versions: 2.1.7 Reporter: Alan M. Carroll Assignee: Alan M. Carroll Priority: Minor Fix For: Doc 3.0 The Alternate Languages links are auto-generated rather than being embedded in the source content files. This creates the problem that the phrase Alternate Languages can't be translated too. The template should be changed to have pull the phrase from a variable and default to Alternate Languages. This way it's always there, but translated files can override it in order to translate it. It would have to be done for every translated file, but that's no worse than the previous system which required it for every file, translated or not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-406) manual for traffic shell not installed during make install
[ https://issues.apache.org/jira/browse/TS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449336#comment-13449336 ] Daniel Gruno commented on TS-406: - There seems to be a man page for this in 3.2.0 and above. Is this correct (and if so, can we fix/close this)? manual for traffic shell not installed during make install Key: TS-406 URL: https://issues.apache.org/jira/browse/TS-406 Project: Traffic Server Issue Type: Task Components: Documentation Affects Versions: 2.1.2, 2.0.0 Environment: linux Reporter: Conan Wang Priority: Trivial Fix For: Doc 3.0 the command man traffic_shell returns No manual entry for traffic_line, in both release and trunk version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-289) should we get rid of type index?
[ https://issues.apache.org/jira/browse/TS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449341#comment-13449341 ] Daniel Gruno commented on TS-289: - +1 to getting rid of. We don't have this in the 3.0 docs, so this should be easy to fix ;) should we get rid of type index? Key: TS-289 URL: https://issues.apache.org/jira/browse/TS-289 Project: Traffic Server Issue Type: Improvement Components: Documentation Reporter: Miles Libbey Fix For: Doc 3.0 http://incubator.apache.org/trafficserver/docs/v2/sdk/TypeIndex.html seems pretty worthless, and unlikely anyone will maintain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-436) Documenttation for variable hardware sector size support
[ https://issues.apache.org/jira/browse/TS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449350#comment-13449350 ] Daniel Gruno commented on TS-436: - Description of it has been added to http://trafficserver.apache.org/docs/trunk/admin/configuration-files/records.config (and since fixed, since it was initially wrong). Does it need more elaboaration, or will people get the gist of it? We could add the long description supplied in this ticket to it, but that might seem a bit out of place compared to the other config field descriptions. Thoughts, suggestions? Documenttation for variable hardware sector size support Key: TS-436 URL: https://issues.apache.org/jira/browse/TS-436 Project: Traffic Server Issue Type: Improvement Components: Documentation Affects Versions: 2.1.6 Reporter: John Plevyak Assignee: Miles Libbey Fix For: Doc 3.0 TS-43 Adds support for auto-detecting drives which have 4096 (well, between 512-8192) sector size and using that as the element of atomicity in the cache. Add (optional/hidden) config: CONFIG proxy.config.cache.force_sector_size INT to force a sector size (e.g. 4096) for ALL disks. SSDs and advanced format drives lie about their sector size and claim 512. The handling of this is still in flux in linuxland hence the option to force a particular sector size. Note: it is safe to force a higher size than the hardware supports natively as we still only count on atomicity in 512 byte increments. 4096 sector size drives formatted for windows will have partitions aligned on 63 512 byte sector boundaries which will mean they will be unaligned.. There are workarounds, but you need to do some research on your particular drive. For example, some drives have a one time option to switch the partition boundary, others might require reformatting or repartitioning. To be safe in Linux you could just use the entire drive: /dev/sdb instead of /dev/sdb1 and TS will do the right thing. This feature should work fine when we get out of the difficult transition stage, in the mean time caveat emptor. Partitions formatted to support hardware sector size of more than 512 (e.g. 4096) will result in all objects stored in the cache to be integral multiples of 4096 bytes which will result in some waste for small files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
