Unknown time zone 'posixrules'

[YangKeao]

Bug Report

1. What did you do?

Start tikv, pd and tidb on a machine with America/New_York timezone. (Ubuntu 18.04)

2. What did you expect to see?

TiDB starts normally.

3. What did you see instead?

TiDB fails to start. Return an error from tikv coprocessor: Unknown time zone 'posixrules'.

This was because on some distribution, /etc/localtime was linked to /usr/share/zoneinfo/America/New_York which was also a soft link to /usr/share/zoneinfo/posixrules.

Then TiKV receives posixrules timezone and fails to parse it.

A simple way to fix it is to readlink only once (but filepath.EvalSymlinks actually follows the symlink recursively).

[qw4990]

@YangKeao Thanks for your feedback, could you please post the error message and error stack to us?

[YangKeao]

@qw4990

[2020/03/26 08:27:25.641 -04:00] [WARN] [coprocessor.go:947] ["other error"] [txnStartTS=415557391642787847] [regionID=48] [storeAddr=127.0.0.1:20160] [error="other error: [components/tidb_query/src/expr/ctx.rs:87]: unknown or incorrect time zone: posixrules"]
[2020/03/26 08:27:25.642 -04:00] [FATAL] [terror.go:348] ["unexpected error"] [error="other error: [components/tidb_query/src/expr/ctx.rs:87]: unknown or incorrect time zone: posixrules"] [stack="github.com/pingcap/log.Fatal\n\t/home/jenkins/agent/workspace/tidb_master/go/pkg/mod/github.com/pingcap/log@v0.0.0-20200117041106-d28c14d3b1cd/global.go:59\ngithub.com/pingcap/parser/terror.MustNil\n\t/home/jenkins/agent/workspace/tidb_master/go/pkg/mod/github.com/pingcap/parser@v0.0.0-20200317021010-cd90cc2a7d87/terror/terror.go:348\nmain.createStoreAndDomain\n\t/home/jenkins/agent/workspace/tidb_master/go/src/github.com/pingcap/tidb/tidb-server/main.go:235\nmain.main\n\t/home/jenkins/agent/workspace/tidb_master/go/src/github.com/pingcap/tidb/tidb-server/main.go:171\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"]

[shenoy-anurag]

Has this been fixed and is there any workaround?

[ti-srebot]

Please edit this comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

[ti-srebot]

(RCA AllTriggerConditions FixedVersions AffectedVersions Symptom ) fields are empty.

[ti-srebot]

( FixedVersions AffectedVersions ) fields are empty.